nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
A side-by-side editorial comparison of Casdoor and survivoR — 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.
A Survivor data package that keeps turning a TV show into a relational database
survivoR ships Survivor franchise data as R data frames covering the US, Australian, UK and New Zealand versions. Recent releases track broadcast: US48, US49 and US50 arrived across 2.3.6, 2.3.9 and 2.3.12, alongside AU09, AU12 and Australia vs. The World. The 2.3.12 release also reworked castaway_scores into an explicit three-tier structure - standardised residual scores, probabilistic scores bounded on [0,1], and combined scores - and added advantage_timeline as a long-format view of advantage movement.
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.
survivoR ships Survivor franchise data as R data frames covering the US, Australian, UK and New Zealand versions. Recent releases track broadcast: US48, US49 and US50 arrived across 2.3.6, 2.3.9 and 2.3.12, alongside AU09, AU12 and Australia vs. The World. The 2.3.12 release also reworked castaway_scores into an explicit three-tier structure - standardised residual scores, probabilistic scores bounded on [0,1], and combined scores - and added advantage_timeline as a long-format view of advantage movement.
The work is less about adding seasons than about making the tables join cleanly. 2.3.1 rebuilt challenge_description and challenge_results around a shared challenge_id, added challenge characteristic flags and result notes, and put logical finalist, winner and jury flags on castaways. Since then the pattern repeats at smaller scale: boot_order as its own table, season_name deprecated everywhere except season_summary, castaways cleaned so people booted twice appear once. Derived analytical columns are being separated from raw records rather than mixed into them.
Expect the next release to add the current season's data on the same broadcast-following cadence, with any structural work continuing to split derived scores out of the raw tables.
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 survivoR.
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 survivoR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Casdoor is currently shipping more aggressively (velocity 5.0 vs 0.0), 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. Casdoor is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 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 survivoR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "survivoR alternatives" section above for the current picks, or visit /alternatives/survivor for the full list with editorial commentary on each.