How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 20:11 UTC·Repo last pushed today
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
61.0k
Forks
6.6k
Last Push
2026-06-04
today
Commits (4 wk)
57
Downloads (7d)
—
HN mentions (30d)
0
Open Issues
323
Rank Change
▼12
was #143
Analysis
HVTrust Dimensions
47.6 / 100 · 75.0% confidence
Safety / IntegrityOSSF, provenance, signatures
9.3 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.8 / 17
MaintenanceFreshness and commits
19.0 / 20
AdoptionStars and downloads
11.5 / 20
Activity Inputs
93.5 / 100
StarsRepository reach
28.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
22.0 / 25
CommunityFork signal
17.8 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.0 / 10
via deps.dev · OpenSSF
Signed Commits
61%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection0
CI-Tests7
CII-Best-Practices0
Code-Review3
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies1
SAST0
Security-Policy10
Signed-Releases0
Token-Permissions0
Vulnerabilities10
Is AnythingLLM safe?
Public trust evidence for AnythingLLM is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does AnythingLLM publish package provenance?
No published build provenance is currently detected for AnythingLLM. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does AnythingLLM have an OpenSSF Scorecard?
AnythingLLM has an OpenSSF Scorecard score of 5.0/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 AnythingLLM actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does AnythingLLM use?
AnythingLLM ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are AnythingLLM's commits signed?
61% of the last 100 commits to AnythingLLM 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 AnythingLLM?
HVTrust scores AnythingLLM 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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OSSF Scorecard via deps.dev · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
