Is nxtg-ai/forge-orchestrator still actively maintained? (July 2026)
No, not actively. nxtg-ai/forge-orchestrator is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.
- Last commit2 months ago (May 6, 2026)
- Contributors2
- Stars128 (+0 in last 7 days)
- Star delta (30d)+6 in last 30 days
- Velocity score0.0/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 nxtg-ai/forge-orchestrator still actively maintained? (July 2026)
No, not actively. nxtg-ai/forge-orchestrator is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.
How is beam classifying nxtg-ai/forge-orchestrator?
Beam classifies nxtg-ai/forge-orchestrator as dying with a velocity score of 0.0/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 nxtg-ai/forge-orchestrator?
The most recent commit to nxtg-ai/forge-orchestrator was 2 months ago (May 6, 2026).
How can I track nxtg-ai/forge-orchestrator's status going forward?
Beam refreshes nxtg-ai/forge-orchestrator's velocity score and class daily. The live tool profile is at /tools/1570; the JSON API endpoint is /api/v1/tools/1570.