@n8n/cli
[beta] Client CLI for n8n — manage workflows, executions, and credentials from the terminal
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @n8n package from n8n-io org; Levenshtein match to 'joi' is coincidental, not impersonation. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 1 / 4 | |
| 0.5.0 | 1 / 4 | |
| 0.4.0 | 1 / 4 | |
| 0.3.0 | 1 / 3 | |
| 0.2.0 | 1 / 3 | |
| 0.1.0 | 1 / 3 |
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.