Is weaviate/weaviate-python-client still actively maintained? (July 2026)
No, not actively. weaviate/weaviate-python-client is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.
- Last commit12 days ago (June 24, 2026)
- Contributors79
- Stars226 (+0 in last 7 days)
- Star delta (30d)+0 in last 30 days
- Velocity score0.0/10 (dying)
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 →
Is weaviate/weaviate-python-client still actively maintained? (July 2026)
No, not actively. weaviate/weaviate-python-client is classified dying on beam — contributor count is shrinking and commits have slowed. Current velocity score: 0.0/10.
How is beam classifying weaviate/weaviate-python-client?
Beam classifies weaviate/weaviate-python-client 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 weaviate/weaviate-python-client?
The most recent commit to weaviate/weaviate-python-client was 12 days ago (June 24, 2026).
How can I track weaviate/weaviate-python-client's status going forward?
Beam refreshes weaviate/weaviate-python-client's velocity score and class daily. The live tool profile is at /tools/1866; the JSON API endpoint is /api/v1/tools/1866.