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 Brhiza/mingyu
[STATUS / STABLE]

Is Brhiza/mingyu still actively maintained? (September 2026)

Yes. Brhiza/mingyu is classified stable on beam — healthy maintenance, no momentum loss. Current velocity score: 0.9/10.

What the signals say
  • Last commit6 days ago (September 21, 2026)
  • Contributors4
  • Stars437 (+16 in last 7 days)
  • Star delta (30d)+87 in last 30 days
  • Velocity score0.9/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 Brhiza/mingyu still actively maintained? (September 2026)

Yes. Brhiza/mingyu is classified stable on beam — healthy maintenance, no momentum loss. Current velocity score: 0.9/10.

How is beam classifying Brhiza/mingyu?

Beam classifies Brhiza/mingyu as stable with a velocity score of 0.9/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 Brhiza/mingyu?

The most recent commit to Brhiza/mingyu was 6 days ago (September 21, 2026).

How can I track Brhiza/mingyu's status going forward?

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

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