Is tursodatabase/agentfs still actively maintained? (October 2026)
No, not actively. tursodatabase/agentfs is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.1/10.
- Last commit4 months ago (June 3, 2026)
- Contributors22
- Stars3,419 (+14 in last 7 days)
- Star delta (30d)+48 in last 30 days
- Velocity score0.1/10 (dying)
Dying means contributors have dropped, commits have gone silent, or the score has fallen into the bottom decile and is still falling. Beam flags this aggressively because GitHub-star inertia hides decay. Full methodology →
Is tursodatabase/agentfs still actively maintained? (October 2026)
No, not actively. tursodatabase/agentfs is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.1/10.
How is beam classifying tursodatabase/agentfs?
Beam classifies tursodatabase/agentfs as dying with a velocity score of 0.1/10. Beam fuses code activity, package adoption, sentiment, research citation, and production signals into a single 0–10 score; the classification thresholds are explained on /about.
When was the last commit to tursodatabase/agentfs?
The most recent commit to tursodatabase/agentfs was 4 months ago (June 3, 2026).
How can I track tursodatabase/agentfs's status going forward?
Beam refreshes tursodatabase/agentfs's velocity score and class daily. The live tool profile is at /tools/458; the JSON API endpoint is /api/v1/tools/458.