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 bug-ops/zeph
[STATUS / STABLE]

Is bug-ops/zeph still actively maintained? (September 2026)

Yes. bug-ops/zeph is classified stable on beam — healthy maintenance, no momentum loss. Current velocity score: 0.0/10.

What the signals say
  • Last commit6 days ago (September 21, 2026)
  • Contributors2
  • Stars60 (+1 in last 7 days)
  • Star delta (30d)+4 in last 30 days
  • Velocity score0.0/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 bug-ops/zeph still actively maintained? (September 2026)

Yes. bug-ops/zeph is classified stable on beam — healthy maintenance, no momentum loss. Current velocity score: 0.0/10.

How is beam classifying bug-ops/zeph?

Beam classifies bug-ops/zeph as stable 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 bug-ops/zeph?

The most recent commit to bug-ops/zeph was 6 days ago (September 21, 2026).

How can I track bug-ops/zeph's status going forward?

Beam refreshes bug-ops/zeph's velocity score and class daily. The live tool profile is at /tools/208907; the JSON API endpoint is /api/v1/tools/208907.

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