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 yegor256/prompt
[STATUS / DYING]

Is yegor256/prompt still actively maintained? (May 2026)

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

What the signals say
  • Last commit6 days ago (May 16, 2026)
  • Contributors3
  • Stars142 (+0 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 yegor256/prompt still actively maintained? (May 2026)

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

How is beam classifying yegor256/prompt?

Beam classifies yegor256/prompt 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 yegor256/prompt?

The most recent commit to yegor256/prompt was 6 days ago (May 16, 2026).

How can I track yegor256/prompt's status going forward?

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

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