GSD
Tracked across 24 snapshots (2026-02-09 → 2026-06-12).
Rating timeline
Dimension trajectory
Autonomy
10/20Integration
7/20Context
11/20Compliance
4/20Viability
2/20Interface
10/20Cap timeline
Notable events
- 2026-04-09Cap +no-codebase-indexing
- 2026-04-09Cap −no-automation-mode
- 2026-04-20Cap −no-enterprise-features
- 2026-04-20Cap −no-codebase-indexing
- 2026-05-04Cap +no-enterprise-features
- 2026-05-04Cap +no-codebase-indexing
- 2026-05-04Drop-7 rating
- 2026-05-05Jump+7 rating
- 2026-05-16Cap −no-enterprise-features
- 2026-05-16Cap −no-codebase-indexing
- 2026-05-28SignalTracked → Detected
- 2026-05-28Cap +funding-concerns
- 2026-05-28Cap +community-exodus
- 2026-05-28Cap +stalled-development
- 2026-05-28Cap +severe-negative-sentiment
- 2026-05-28Cap +no-codebase-indexing
- 2026-05-28Drop-8 rating
What would move this next
Upgrade if: open-gsd/get-shit-done-redux establishes durable multi-maintainer governance with sustained release cadence and rebuilds community trust (re-engagement, star recovery on the canonical fork); advisory-only security hooks replaced with hard-enforcement circuit breakers; abandoned original npm packages removed/deprecated by registry; independent security validation of the redux fork with the systemic findings (npm ownership gap, @-file exfiltration vector, broad agent permissions) closed. Downgrade further / drop coverage if: redux fork stalls (no releases 90+ days), supply-chain incident exploits the live abandoned packages, or community fragments across multiple incompatible forks with no clear canonical line.