Teamhood
Teamhood's recent feed is all comparison SEO, leaning hard into construction PM
A side-by-side editorial comparison of Kanboard and Leantime — release velocity, themes, recent moves, and the top alternatives to consider.
Kanboard is on a year-long security-hardening run, sweeping the codebase one attack class at a time.
Kanboard's last six releases read as a single sustained security audit: parameterized queries replacing raw SQL, SSRF protection for webhooks, LDAP injection escapes, timing-safe token comparisons, CSRF for project role changes, comment-visibility enforcement for unauthenticated users, and removal of unsafe deserialization paths (file cache driver, legacy serialized events). Feature work continues in parallel — RTL support, Arabic translation, sub-task counts, bulk tag operations — but is clearly secondary to the hardening arc.
Leantime hardens its new permission engine through a rapid-fire auth patch cycle.
Leantime just shipped 3.9.0, a ground-up permission engine that replaced ad-hoc role checks with centralized, fail-closed authorization across every domain, landing alongside a JSON-RPC API layer and mobile push tokens. The 3.9.1 through 3.9.4 point releases that followed are almost entirely auth stabilization: Bearer and personal-access-token authentication broke under the new Sanctum guard and took four patches to fully settle. The project is mid-transition from a legacy PHP codebase to a modern Laravel, Blade, and JSON-RPC stack.
Kanboard's last six releases read as a single sustained security audit: parameterized queries replacing raw SQL, SSRF protection for webhooks, LDAP injection escapes, timing-safe token comparisons, CSRF for project role changes, comment-visibility enforcement for unauthenticated users, and removal of unsafe deserialization paths (file cache driver, legacy serialized events). Feature work continues in parallel — RTL support, Arabic translation, sub-task counts, bulk tag operations — but is clearly secondary to the hardening arc.
The team is methodically working through input surfaces (LDAP, headers, webhooks, file uploads, redirect targets) and output surfaces (comments, exports, API responses) to close authorization and injection gaps. This is mature-project hygiene, not pivot work — Kanboard is positioning itself as an audit-ready self-hostable kanban for organizations with security review checklists. PHP 8.1 is now the floor; the codebase is being modernized alongside the hardening.
Expect the security cadence to continue with one to two more releases focused on remaining trust boundaries, then a feature-weighted release picking up RTL/locale follow-ons and possibly the long-promised SQLite/Postgres parity work hinted at by recent Docker Compose additions.
Leantime just shipped 3.9.0, a ground-up permission engine that replaced ad-hoc role checks with centralized, fail-closed authorization across every domain, landing alongside a JSON-RPC API layer and mobile push tokens. The 3.9.1 through 3.9.4 point releases that followed are almost entirely auth stabilization: Bearer and personal-access-token authentication broke under the new Sanctum guard and took four patches to fully settle. The project is mid-transition from a legacy PHP codebase to a modern Laravel, Blade, and JSON-RPC stack.
The direction is a comprehensive backend re-architecture, with the permission engine, JSON-RPC API, completed Blade template unification, and experimental Postgres support all converging on a cleaner, API-first core. The recent burst of Bearer-auth fixes shows the team paying down the regressions the permission-engine rollout introduced rather than adding new surface. Mobile is the next frontier: the 3.8.0 TestFlight API groundwork and 3.9.0 push tokens point to a native app nearing release.
Expect the auth-fix cadence to slow as the Bearer regressions settle, with attention shifting toward the mobile app's public launch and broader JSON-RPC endpoint coverage.
Other PM 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 Kanboard or Leantime.
Teamhood's recent feed is all comparison SEO, leaning hard into construction PM
Celoxis's feed is SEO comparison articles, not product releases
HoneyBook's feed is blog and competitor-comparison content, not a product release log
Atlassian threads Rovo AI through the developer loop while its blog leans on case studies
Unito's tracked feed is its content-marketing blog, not a product changelog — no shipped moves to read.
Planview's feed is strategic-portfolio thought leadership, not release notes — product signal is absent.
See all Kanboard alternatives → · See all Leantime alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Leantime is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. Leantime is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other PM products to evaluate alongside.
Top Kanboard alternatives in PM are ranked by recent ship velocity. Browse the "Kanboard alternatives" section above for the current picks, or visit /alternatives/kanboard for the full list with editorial commentary on each.
Top Leantime alternatives in PM are ranked by recent ship velocity. Browse the "Leantime alternatives" section above for the current picks, or visit /alternatives/leantime for the full list with editorial commentary on each.