updated 2026-10-09 16:07 UTC

n8n

Repository Website

Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.

Workflow Platforms TypeScript Listed NOASSERTION Source-available

Is n8n safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.7 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare n8n

How does it stack up against its Workflow Platforms neighbours?

Pick any agent to compare →
Suggest a correction

In detail: n8n scores 91.5/100 (Grade A), ranked #14 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.7/10; 100% of recent commits are signed; no published advisory affects its latest release (n8n); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How n8n could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships n8n and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/n8n-io/n8n, NOASSERTION, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.7/10 (scanned Oct 9, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection4
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies7
    All 14 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CII-Best-Practices 0
    Code-Review 10
    Dangerous-Workflow 10
    Fuzzing 10
    License 9
    Maintained 10
    Packaging 10
    Pinned-Dependencies 7
    SAST 1
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0

  3. Published packages Linked and attested

    • npm n8n Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: n8n 2.42.6. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of n8n.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues n8n’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How n8n compares in Workflow Platforms

  1. #1 n8n 91.5 this agent
  2. #2 Botpress 86.8 −4.7
  3. #3 Trigger.dev 86.8 −4.7
  4. #4 Hypit 81.3 −10.2
  5. #5 Dify 79.1 −12.4

Bars show each HVTrust score; the tick marks n8n’s 91.5.

Where the 91.5 comes from

HVTrust dimensions vs the Workflow Platforms average

91.5 / 100 · 100.0% confidence

n8n Workflow Platforms average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.9 / 25
10.4 above avg 10.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.1 above avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
14.2 / 17
1.7 above avg 12.5
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
3.0 above avg 17.0
AdoptionLog-scaled stars · package downloads
20.0 / 20
7.2 above avg 12.8

Quick Trust Read

What Would Improve It
Improve transparency to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.7/10. Tighten the weakest checks to improve public safety evidence.
Compare with Botpress Get email alerts for n8n View Workflow Platforms Report missing data
100.0
Activity sub-score · out of 100
#1
In Workflow Platforms

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

Signals refreshed 2026-10-09 16:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
206.8k
Forks
61.0k
Last Push
2026-10-09
today
Commits (4 wk)
1483
Downloads (7d)
269,560,600
npm+docker
HN mentions (30d)
275
Open Issues
360
Rank Change
=
was #14

Analysis

Activity Inputs

100.0 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
20 / 20

Common questions about n8n

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.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 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?
100% 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.

Compare n8n head-to-head

n8n vs Botpress → n8n vs Trigger.dev → n8n vs Hypit →

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
high confidence
Implemented
n8n appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
6 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • code
  • database
  • shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to n8n's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Browserbase, Mistral AI
2026-09-03
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI

Maintain n8n?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Surface 1Surface 1
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Browserbase, Mistral AI
2026-09-03
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
GitHub → Website → npm: n8n

Embed Badge Badge guide for maintainers →

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

Other agents in Workflow Platforms

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.4 · Raw JSON