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 SapienzaNLP/relik
[STATUS / DYING]

Is SapienzaNLP/relik still actively maintained? (May 2026)

No, not actively. SapienzaNLP/relik 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 months ago (July 29, 2025)
  • Contributors7
  • Stars501 (+1 in last 7 days)
  • Star delta (30d)+2 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 SapienzaNLP/relik still actively maintained? (May 2026)

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

How is beam classifying SapienzaNLP/relik?

Beam classifies SapienzaNLP/relik 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 SapienzaNLP/relik?

The most recent commit to SapienzaNLP/relik was 10 months ago (July 29, 2025).

How can I track SapienzaNLP/relik's status going forward?

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

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