@n8n/backend-network
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): n8n monorepo publishes via GitHub Actions CI/CD with SLSA attestation; publisher-changed from human to GHA is expected and documented. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): reflect-metadata is a known implicit/side-effect import for decorator metadata; not directly imported by design. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal n8n scoped package; sparse README and no keywords are expected for internal monorepo packages. | ai |
v1.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-06-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.