beam
beam
Discover
PulseActivityAnalyticsBest forMapOrgs
Niches
AgentsMCPRAGCoding AssistantsInference & Serving
Personal
WatchlistCompare
?
Sign in
magic link · no password
LIVE──────── · ──:──:── UTCabout
beam
beam
Discover
PulseActivityAnalyticsBest forMapOrgs
Niches
AgentsMCPRAGCoding AssistantsInference & Serving
Personal
WatchlistCompare
?
Sign in
magic link · no password
Back to RTGS2017/NagaAgent
[STATUS / DYING]

Is RTGS2017/NagaAgent still actively maintained? (May 2026)

No, not actively. RTGS2017/NagaAgent is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.

What the signals say
  • Last commit12 days ago (May 10, 2026)
  • Contributors14
  • Stars1,515 (-1 in last 7 days)
  • Star delta (30d)-1 in last 30 days
  • Velocity score0.0/10 (dying)
What ‘dying’ means on beam

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 →

Frequently asked

Is RTGS2017/NagaAgent still actively maintained? (May 2026)

No, not actively. RTGS2017/NagaAgent is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.

How is beam classifying RTGS2017/NagaAgent?

Beam classifies RTGS2017/NagaAgent 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 RTGS2017/NagaAgent?

The most recent commit to RTGS2017/NagaAgent was 12 days ago (May 10, 2026).

How can I track RTGS2017/NagaAgent's status going forward?

Beam refreshes RTGS2017/NagaAgent's velocity score and class daily. The live tool profile is at /tools/514; the JSON API endpoint is /api/v1/tools/514.

Full tool profile Methodology API
LIVE──────── · ──:──:── UTCabout