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

Is kserve/kserve still actively maintained? (July 2026)

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

What the signals say
  • Last committoday (July 6, 2026)
  • Contributors364
  • Stars5,656 (+27 in last 7 days)
  • Star delta (30d)+107 in last 30 days
  • Velocity score2.7/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 kserve/kserve still actively maintained? (July 2026)

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

How is beam classifying kserve/kserve?

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

The most recent commit to kserve/kserve was today (July 6, 2026).

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

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

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