Versioned security assessment

Report ID: SA-73E2D35A

6/27/2026, 6:19:29 PM

n8n security assessment v4

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
n8n
Version
v4
Maintainer
Joseph OBrien
Coverage
3 Files scanned · 366 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Static findings were mostly false positives caused by Markdown code fences, n8n node type names, placeholder files, and example URLs. The confirmed risk is legitimate but sensitive use of curl commands with an n8n API key to list, create, update, activate, deactivate, and inspect workflow executions. No prompt injection, malicious exfiltration, obfuscation, or unauthorized credential harvesting was found.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

3 Files scanned · 366 Lines analyzed

2 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 10 evidence locations

Filesystem access

May read or write local files.

Not recorded by this audit

Env variables

May read values from the process environment.

Observed in 8 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 6 evidence locations

Capability review items (2)
Medium
Workflow Administration Through API Key Commands
The skill includes curl examples that use X-N8N-API-KEY to list, create, update, activate, deactivate, and inspect workflows. This is legitimate n8n administration guidance, but misuse could modify automations or expose execution data.
The commands are explicit documentation for n8n REST API administration and include an API key header. They target localhost, so the risk is sensitive operational capability rather than confirmed malicious intent.
Medium
External API Request Pattern
The skill demonstrates an HTTP Request node that posts workflow data to an external API using n8n credentials. This is expected for automation workflows, but users must verify destination URLs and data minimization.
The example shows a generic external URL and credential-backed request. It is a normal n8n pattern, but it can move workflow data outside the n8n instance when adapted.

Risk findings

Confirmed security concerns are separated from items that still need review.

No confirmed security findings were recorded for this completed audit.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (2)
Low
Static Weak Crypto Findings Are False Positives
The weak cryptographic algorithm alerts correspond to ordinary n8n terminology, Markdown placeholder text, and node type strings. No cryptographic implementation or weak hashing use was found.
Reviewed context shows these alerts are caused by prose and example names, not cryptographic code. No hashing, encryption, or password storage behavior appears in the reviewed files.
Low
Markdown Code Fence Alerts Are Mostly False Positives
Most external command alerts come from JSON examples, inline n8n expressions, and Markdown code fences. The only actionable command examples are documented curl calls for a local n8n API.
The file is documentation and contains no executable script entry point. The static scanner matched formatting and inline examples across many non-shell sections.

Verify and export

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable