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 zgsm-ai/costrict
[STATUS / STABLE]

Is zgsm-ai/costrict still actively maintained? (May 2026)

Yes. zgsm-ai/costrict is classified stable on beam — healthy maintenance, no momentum loss. Current velocity score: 0.3/10.

What the signals say
  • Last commit8 days ago (May 14, 2026)
  • Contributors272
  • Stars4,016 (+23 in last 7 days)
  • Star delta (30d)+42 in last 30 days
  • Velocity score0.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 zgsm-ai/costrict still actively maintained? (May 2026)

Yes. zgsm-ai/costrict is classified stable on beam — healthy maintenance, no momentum loss. Current velocity score: 0.3/10.

How is beam classifying zgsm-ai/costrict?

Beam classifies zgsm-ai/costrict as stable with a velocity score of 0.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 zgsm-ai/costrict?

The most recent commit to zgsm-ai/costrict was 8 days ago (May 14, 2026).

How can I track zgsm-ai/costrict's status going forward?

Beam refreshes zgsm-ai/costrict's velocity score and class daily. The live tool profile is at /tools/2773; the JSON API endpoint is /api/v1/tools/2773.

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