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

Is hummingbot/hummingbot still actively maintained? (September 2026)

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

What the signals say
  • Last commit2 months ago (July 30, 2026)
  • Contributors322
  • Stars20,132 (+113 in last 7 days)
  • Star delta (30d)+558 in last 30 days
  • Velocity score1.4/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 hummingbot/hummingbot still actively maintained? (September 2026)

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

How is beam classifying hummingbot/hummingbot?

Beam classifies hummingbot/hummingbot as stable with a velocity score of 1.4/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 hummingbot/hummingbot?

The most recent commit to hummingbot/hummingbot was 2 months ago (July 30, 2026).

How can I track hummingbot/hummingbot's status going forward?

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

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