nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
A side-by-side editorial comparison of Casdoor and PocketBase — release velocity, themes, recent moves, and the top alternatives to consider.
Casdoor is spending its release cadence moving auth checks from the client to the server
Casdoor is in a tight patch cadence: six tagged releases inside a week, most carrying a single commit. The substance is concentrated in identity enforcement rather than features - password rotation and MFA setup are now enforced server-side, admin updates to a user respect the column whitelist, sessions and tokens are revoked when a user is forbidden, and phone numbers are normalised before they are stored. The remainder is release plumbing and a PostgreSQL query fix.
PocketBase ships small, twice — every 0.39 release gets a matching 0.22 backport for users who never moved.
PocketBase releases every one to two weeks in tight pairs: a 0.39 patch and a 0.22 backport carrying whatever subset applies. The content is consistently small — admin UI fixes, dependency bumps, SQLite and goja updates — with occasional security work. The most consequential recent decision was replacing ozzo-validation with an in-house fork after the upstream library changed ownership.
Casdoor is in a tight patch cadence: six tagged releases inside a week, most carrying a single commit. The substance is concentrated in identity enforcement rather than features - password rotation and MFA setup are now enforced server-side, admin updates to a user respect the column whitelist, sessions and tokens are revoked when a user is forbidden, and phone numbers are normalised before they are stored. The remainder is release plumbing and a PostgreSQL query fix.
Read together, these commits describe one job: closing the gap between what the console enforces and what the backend enforces. Several of them move a check that previously lived in the UI into the server, which is the work of a project being deployed into environments that audit it. New authentication providers and integrations have thinned relative to this hardening pass.
The next releases most likely continue the same sweep - remaining endpoints where an admin or user request is trusted more than the server verifies - rather than adding a new identity provider.
PocketBase releases every one to two weeks in tight pairs: a 0.39 patch and a 0.22 backport carrying whatever subset applies. The content is consistently small — admin UI fixes, dependency bumps, SQLite and goja updates — with occasional security work. The most consequential recent decision was replacing ozzo-validation with an in-house fork after the upstream library changed ownership.
This is a mature single-maintainer project in steady maintenance, prioritizing dependency hygiene and supply-chain caution over new capability. Two things are explicitly deferred to the future: proper non-zero exit code support for CLI commands, held back to v0.40 or v0.41 after a panic-recovery change was reverted, and eventually replacing ozzo-validation with a purpose-built validator. The continued 0.22 backports show a real installed base that hasn't migrated.
The deferred CLI exit-code work marks v0.40 as the next feature release rather than another patch. Expect the 0.39 and 0.22 pairing to continue until 0.22 is formally retired.
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 Casdoor or PocketBase.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
See all Casdoor alternatives → · See all PocketBase alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Casdoor and PocketBase are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Casdoor and PocketBase are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Casdoor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Casdoor alternatives" section above for the current picks, or visit /alternatives/casdoor for the full list with editorial commentary on each.
Top PocketBase alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PocketBase alternatives" section above for the current picks, or visit /alternatives/pocketbase for the full list with editorial commentary on each.