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 CLUEbenchmark/CLUE
[STATUS / DYING]

Is CLUEbenchmark/CLUE still actively maintained? (May 2026)

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

What the signals say
  • Last commit4 months ago (February 6, 2026)
  • Contributors24
  • Stars4,254 (-2 in last 7 days)
  • Star delta (30d)+0 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 CLUEbenchmark/CLUE still actively maintained? (May 2026)

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

How is beam classifying CLUEbenchmark/CLUE?

Beam classifies CLUEbenchmark/CLUE 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 CLUEbenchmark/CLUE?

The most recent commit to CLUEbenchmark/CLUE was 4 months ago (February 6, 2026).

How can I track CLUEbenchmark/CLUE's status going forward?

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

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