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 neuml/rag
[STATUS / DYING]

Is neuml/rag still actively maintained? (May 2026)

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

What the signals say
  • Last commit6 months ago (December 1, 2025)
  • Contributors1
  • Stars450 (+1 in last 7 days)
  • Star delta (30d)+2 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 neuml/rag still actively maintained? (May 2026)

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

How is beam classifying neuml/rag?

Beam classifies neuml/rag 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 neuml/rag?

The most recent commit to neuml/rag was 6 months ago (December 1, 2025).

How can I track neuml/rag's status going forward?

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

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