beam
beam
Discover
PulseActivityAnalyticsBest forMapOrgs
Niches
AgentsMCPRAGCoding AssistantsInference & ServingVector DBs
Personal
WatchlistCompareWeekly report
?
Sign in
magic link · no password
LIVE──────── · ──:──:── UTCabout
beam
beam
Discover
PulseActivityAnalyticsBest forMapOrgs
Niches
AgentsMCPRAGCoding AssistantsInference & ServingVector DBs
Personal
WatchlistCompareWeekly report
?
Sign in
magic link · no password
Back to judge0/judge0
[STATUS / STABLE]

Is judge0/judge0 still actively maintained? (August 2026)

Yes. judge0/judge0 is classified stable on beam — healthy maintenance, no momentum loss. Current velocity score: 1.3/10.

What the signals say
  • Last commit3 days ago (August 17, 2026)
  • Contributors22
  • Stars4,388 (+16 in last 7 days)
  • Star delta (30d)+63 in last 30 days
  • Velocity score1.3/10 (stable)
What ‘stable’ means on beam

Stable means the repo’s velocity score has been consistent over the last 7 days — healthy maintenance signals, no momentum loss, no contributor drop-off. Full methodology →

Frequently asked

Is judge0/judge0 still actively maintained? (August 2026)

Yes. judge0/judge0 is classified stable on beam — healthy maintenance, no momentum loss. Current velocity score: 1.3/10.

How is beam classifying judge0/judge0?

Beam classifies judge0/judge0 as stable with a velocity score of 1.3/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 judge0/judge0?

The most recent commit to judge0/judge0 was 3 days ago (August 17, 2026).

How can I track judge0/judge0's status going forward?

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

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