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 larq/compute-engine
[STATUS / DYING]

Is larq/compute-engine still actively maintained? (May 2026)

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

What the signals say
  • Last commit11 days ago (May 11, 2026)
  • Contributors18
  • Stars251 (+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 larq/compute-engine still actively maintained? (May 2026)

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

How is beam classifying larq/compute-engine?

Beam classifies larq/compute-engine 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 larq/compute-engine?

The most recent commit to larq/compute-engine was 11 days ago (May 11, 2026).

How can I track larq/compute-engine's status going forward?

Beam refreshes larq/compute-engine's velocity score and class daily. The live tool profile is at /tools/2995; the JSON API endpoint is /api/v1/tools/2995.

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