AnythingLLM

Stop renting your intelligence. Own it with AnythingLLM. Everything you need for a powerful local-first agent experience

Memory & Knowledge JavaScript Grade D Listed MIT
43.2/100
Rank #561 of 1283
Compare AnythingLLM

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-13 · 2d ago
Recent change
Rank +2

Is AnythingLLM safe? AnythingLLM scores 43.2/100 (Grade D), ranked #561 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.9/10; 58% of recent commits are signed; last pushed 2026-08-13. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-13
Rank Moved
Rank dropped 14 spots (#558 → #572)
2026-08-10
Rank Moved
Rank dropped 18 spots (#543 → #561)
2026-08-08
Rank Moved
Rank dropped 162 spots (#375 → #537)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
94.7
Activity sub-score · out of 100
#38

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. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-15 10:11 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars
64.7k
Forks
7.1k
Last Push
2026-08-13
2 days ago
Commits (4 wk)
69
Downloads (7d)
HN mentions (30d)
0
Open Issues
294
Rank Change
▲7
was #568

Analysis

HVTrust Dimensions vs Memory & Knowledge

43.2 / 100 · 75.0% confidence

AnythingLLM Memory & Knowledge average (42 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.0 / 25
1.1 below avg 10.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.4 below avg 12.2
Transparency50% declared license · 50% OSSF Scorecard
12.7 / 17
in line with avg 12.5
Maintenance60% last-push freshness · 40% commit activity
19.2 / 20
1.5 above avg 17.7
AdoptionLog-scaled stars · package downloads
11.5 / 20
2.1 below avg 13.6

Activity Inputs

94.7 / 100
StarsRepository reach
28.9 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
23.0 / 25
CommunityFork signal
17.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.9 / 10
OpenSSF Scorecard · scanned Aug 14, 2026
Signed Commits
58%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 7
CII-Best-Practices 0
Code-Review 4
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 1
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 8

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 4.9/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 2 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?
57% 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.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
7 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
  • browser
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain AnythingLLM?

For maintainers

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.

Reputation Timeline

Signal history
Rank 13HVTrust 2Grade 1Scorecard 1Score 1
2026-08-13
Rank Moved
Rank dropped 14 spots (#558 → #572)
2026-08-10
Rank Moved
Rank dropped 18 spots (#543 → #561)
2026-08-08
Rank Moved
Rank dropped 162 spots (#375 → #537)
2026-07-29
Rank Moved
Rank dropped 11 spots (#349 → #360)
2026-07-15
Rank Moved
Rank dropped 20 spots (#323 → #343)
2026-07-14
Rank Moved
Rank dropped 19 spots (#304 → #323)
2026-07-13
Rank Moved
Rank dropped 34 spots (#270 → #304)
2026-06-24
Rank Moved
Rank dropped 31 spots (#211 → #242)
2026-06-23
Rank Moved
Rank dropped 13 spots (#198 → #211)
2026-06-21
Rank Moved
Rank dropped 10 spots (#179 → #189)
2026-06-18
Rank Moved
Rank dropped 13 spots (#163 → #176)
2026-06-01
Rank Moved
Rank dropped 18 spots (#118 → #136)
2026-05-29
HVTrust Changed
HVTrust up 7.5pts (39.7 → 47.2)
2026-05-28
Activity Score Changed
Activity score up 21pts (72 → 92)
2026-05-27
Scorecard Added
OSSF Scorecard: 5.1/10
2026-05-27
Grade Changed
Trust grade D → C
2026-05-27
HVTrust Changed
HVTrust up 14.5pts (38.7 → 53.2)
2026-05-25
Rank Moved
Rank dropped 16 spots (#16 → #32)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 43.2 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/anythingllm.svg)](https://hvtracker.net/agents/anythingllm)
HTML:
<a href="https://hvtracker.net/agents/anythingllm"><img src="https://hvtracker.net/badge/anythingllm.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON