How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 17:27 UTC·Repo last pushed today
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
16.3k
Forks
1.3k
Last Push
2026-06-04
today
Commits (4 wk)
837
Downloads (7d)
35,733,632
pypi
HN mentions (30d)
2
Open Issues
516
Rank Change
▼7
was #37
Analysis
HVTrust Dimensions
75.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.3 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
14.2 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
20.0 / 20
Activity Inputs
89.8 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.5 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.7 / 10
via deps.dev · OpenSSF
Signed Commits
39%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests10
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing10
License10
Maintained10
Packaging10
Pinned-Dependencies8
SAST10
Security-Policy0
Signed-Releases0
Token-Permissions0
Vulnerabilities0
Is Weaviate safe?
Public supply-chain signals for Weaviate are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Weaviate carries less obvious unverified-evidence risk than projects with thin signals.
Does Weaviate publish package provenance?
No published build provenance is currently detected for Weaviate. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Weaviate have an OpenSSF Scorecard?
Weaviate has an OpenSSF Scorecard score of 6.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Weaviate actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Weaviate use?
Weaviate ships under BSD-3-Clause. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Weaviate's commits signed?
39% of the last 100 commits to Weaviate are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Weaviate?
HVTrust scores Weaviate from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
