DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of Casdoor and goodpractice — 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.
The R package-quality checker returns from CRAN limbo with checks you can select by category.
goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.
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.
goodpractice runs a battery of static checks over an R package — style, complexity, test coverage, documentation, DESCRIPTION hygiene — and reports what a reviewer would flag. The package was archived on CRAN, adopted by rOpenSci in 1.0.5, and version 1.1 is the first substantive release since: every check now belongs to one of 16 named groups, discoverable via all_check_groups() and selectable via checks_by_group(), with group-level exclusion through an option or environment variable and new default_checks() and tidyverse_checks() presets.
The direction is from a monolithic verdict toward a configurable one. Previously the practical choices were run everything or name individual checks; grouping makes partial adoption tractable, which matters because the full battery is opinionated enough that teams either accept all of it or ignore the tool. The tidyverse_checks() preset makes that explicit — the package is acknowledging that its defaults encode one house style among several. Earlier releases pointed the same way with a configurable cyclomatic complexity limit and adjustable output length.
With grouping and presets in place, the natural next step is per-project persistent configuration so exclusions live in the repository rather than in an option or environment variable.
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 goodpractice.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox adds a cooling data model — the first new infrastructure domain since power
Two parallel trains, and the 'maintenance' label is now hiding real feature work
See all Casdoor alternatives → · See all goodpractice 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 goodpractice alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "goodpractice alternatives" section above for the current picks, or visit /alternatives/goodpractice for the full list with editorial commentary on each.