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 OpenMOSS/MOSS
[STATUS / DYING]

Is OpenMOSS/MOSS still actively maintained? (July 2026)

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

What the signals say
  • Last commit2 months ago (May 27, 2026)
  • Contributors18
  • Stars12,155 (-1 in last 7 days)
  • Star delta (30d)+18 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 OpenMOSS/MOSS still actively maintained? (July 2026)

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

How is beam classifying OpenMOSS/MOSS?

Beam classifies OpenMOSS/MOSS 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 OpenMOSS/MOSS?

The most recent commit to OpenMOSS/MOSS was 2 months ago (May 27, 2026).

How can I track OpenMOSS/MOSS's status going forward?

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

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