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 Jamailar/RedBox
[STATUS / DYING]

Is Jamailar/RedBox still actively maintained? (July 2026)

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

What the signals say
  • Last commit10 days ago (June 27, 2026)
  • Contributors4
  • Stars1,152 (+0 in last 7 days)
  • Star delta (30d)+110 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 Jamailar/RedBox still actively maintained? (July 2026)

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

How is beam classifying Jamailar/RedBox?

Beam classifies Jamailar/RedBox 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 Jamailar/RedBox?

The most recent commit to Jamailar/RedBox was 10 days ago (June 27, 2026).

How can I track Jamailar/RedBox's status going forward?

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

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