How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed today
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
191.1k
Forks
58.3k
Last Push
2026-06-04
today
Commits (4 wk)
1196
Downloads (7d)
218,716,892
npm+docker
HN mentions (30d)
245
Open Issues
1462
Rank Change
▼1
was #5
Analysis
HVTrust Dimensions
91.8 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
20.1 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
13.7 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
20.0 / 20
Activity Inputs
100.0 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
20 / 20
Supply Chain Trust
Package Provenance
Verified
npm attestation
OSSF Scorecard
6.1 / 10
via deps.dev · OpenSSF
Signed Commits
99%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection4
CI-Tests10
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License9
Maintained10
Packaging10
Pinned-Dependencies7
SAST0
Security-Policy10
Signed-Releases0
Token-Permissions0
Vulnerabilities0
Is n8n safe?
Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. n8n may have internal security practices not visible through public signals.
Public supply-chain signals for n8n are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but n8n carries less obvious unverified-evidence risk than projects with thin signals.
Does n8n publish package provenance?
Yes. n8n's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does n8n have an OpenSSF Scorecard?
n8n has an OpenSSF Scorecard score of 6.1/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 n8n actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does n8n use?
n8n ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are n8n's commits signed?
99% of the last 100 commits to n8n 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.
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 n8n?
HVTrust scores n8n 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
