@n8n-as-code/manager-adapter
Facade adapter from n8n-as-code surfaces to the independent n8n-manager runtime engine
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): Transition from manual publish to GitHub Actions CI/CD; backed by SLSA provenance attestation from the same repo. | ai | |
| provenance | no-provenance | AI (provenance): New package in early development; absence of provenance is common and not a disqualifier here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.0.4 | 3 / 1 | |
| 2.0.3 | 3 / 1 | |
| 2.0.2 | 3 / 1 | |
| 2.0.1 | 3 / 1 | |
| 2.0.0 | 3 / 1 | |
| 0.1.0 | 3 / 1 |
v2.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-06. 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.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-06. 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.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-06. 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.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.