OpenStatus
openstatus is adding the enterprise surface without giving up the self-host story
A side-by-side editorial comparison of SuperTokens and Semgrep — release velocity, themes, recent moves, and the top alternatives to consider.
SuperTokens is building v12 in canary around one hard problem: migrating existing users
The visible releases are all v12.0.x canary builds — no stable v12 in the window. The work concentrates on account linking and a MIGRATED mode for core user directories, with supporting changes for SAML signature-wrapping protection, an activity_log table, and OpenTelemetry span annotations.
Semgrep is spending its releases on parser breadth and scan startup, not new product surface.
Semgrep is shipping a steady weekly-to-biweekly point release on the 1.16x line, and nearly all of the weight sits in the engine rather than the platform. Recent versions widen language and format coverage (OpenTofu .tofu files parsed as Terraform, PHP 8.1-8.5 grammar, Dart typed metavariables, a Ruby tree-sitter bump) and cut the cost of a scan by skipping binary files and statically-dead C/C++ preprocessor branches. A parallel thread of work is pure reliability: the build moved to an OCaml compiler fork to kill nondeterministic crashes and runaway heap growth, and the regex engine consolidated on libpcre2.
The visible releases are all v12.0.x canary builds — no stable v12 in the window. The work concentrates on account linking and a MIGRATED mode for core user directories, with supporting changes for SAML signature-wrapping protection, an activity_log table, and OpenTelemetry span annotations.
The migration-mode thread is the spine here. First new core user directories were allowed to be created as MIGRATED, then the transition into MIGRATED was blocked while inconsistent users exist, then account linking itself was reopened for exploration. That sequence reads as a team discovering that letting a running deployment switch identity models mid-flight is where the correctness risk lives, and adding guardrails before shipping it. Everything else in the window is scaffolding around that: audit-shaped activity logging, tracing annotations, and CI cleanup.
A stable v12 looks gated on the account-linking and migration-mode work settling; expect further canaries tightening the conditions under which a deployment is allowed to change modes before any general release.
Semgrep is shipping a steady weekly-to-biweekly point release on the 1.16x line, and nearly all of the weight sits in the engine rather than the platform. Recent versions widen language and format coverage (OpenTofu .tofu files parsed as Terraform, PHP 8.1-8.5 grammar, Dart typed metavariables, a Ruby tree-sitter bump) and cut the cost of a scan by skipping binary files and statically-dead C/C++ preprocessor branches. A parallel thread of work is pure reliability: the build moved to an OCaml compiler fork to kill nondeterministic crashes and runaway heap growth, and the regex engine consolidated on libpcre2.
The direction is depth over surface area — fewer false positives, fewer crashes, faster startup on large rulesets, and more languages reaching parity with the Pro interfile analysis that already covers Gosu and C/C++. Supply-chain work is advancing quietly alongside it: transitive dependency paths are now exposed behind an experimental flag, and malicious-package findings got their own label in the scan summary. A third strand is org-level control, with a scan-config field that lets the platform disable inline nosemgrep suppressions across an organization.
Expect the experimental --x-dependency-paths flag and the org-wide nosemgrep kill switch to graduate out of experimental status, and more languages to pick up the interfile taint analysis that Gosu just received.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either SuperTokens or Semgrep.
openstatus is adding the enterprise surface without giving up the self-host story
Casdoor ships a minor version per commit, and every one of them is login-flow repair
Authelia's 4.39 line is a long hardening run, not a feature line
Buildkite is rebuilding its CI surface for agents first and clearing the v3 baseline out of the way.
A marketing blog, not a changelog: Unleash is recasting feature flags as agent governance
Okta is documenting its way into agent identity, one Cross App Access guide at a time
See all SuperTokens alternatives → · See all Semgrep alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Semgrep is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Semgrep is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top SuperTokens alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "SuperTokens alternatives" section above for the current picks, or visit /alternatives/supertokens for the full list with editorial commentary on each.
Top Semgrep alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Semgrep alternatives" section above for the current picks, or visit /alternatives/semgrep for the full list with editorial commentary on each.