No, not actively. VectorDB-NTU/Extended-RaBitQ is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.
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 →
No, not actively. VectorDB-NTU/Extended-RaBitQ is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.
Beam classifies VectorDB-NTU/Extended-RaBitQ 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.
The most recent commit to VectorDB-NTU/Extended-RaBitQ was 2 months ago (March 30, 2026).
Beam refreshes VectorDB-NTU/Extended-RaBitQ's velocity score and class daily. The live tool profile is at /tools/1815; the JSON API endpoint is /api/v1/tools/1815.
