@atom8n/n8n-node-dev
CLI to simplify n8n credentials/node development
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atom8n/di | AI (phantom-deps): Declared in dependencies; used transitively by @oclif/core. | ai | |
| phantom-deps | phantom-dep:@atom8n/n8n-core | AI (phantom-deps): Declared in dependencies; used transitively by @oclif/core. | ai | |
| phantom-deps | phantom-dep:@atom8n/n8n-workflow | AI (phantom-deps): Declared in dependencies; used transitively by @oclif/core. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.5.7 | 9 / 2 | |
| 2.5.6 | 9 / 2 | |
| 2.5.5 | 9 / 2 | |
| 2.5.4 | 9 / 2 | |
| 2.5.3 | 9 / 2 | |
| 2.5.2 | 9 / 2 | |
| 2.5.1 | 9 / 2 | |
| 2.5.0 | 9 / 2 | |
| 2.4.3 | 9 / 2 | |
| 2.4.2 | 9 / 2 | |
| 2.4.1 | 9 / 2 | |
| 2.4.0 | 9 / 2 | |
| 2.3.0 | 9 / 2 | |
| 2.2.9 | 9 / 2 | |
| 2.2.8 | 9 / 2 | |
| 2.2.7 | 9 / 2 | |
| 2.2.6 | 9 / 2 | |
| 2.2.5 | 9 / 2 | |
| 2.2.4 | 9 / 2 | |
| 2.2.3 | 9 / 2 | |
| 2.2.2 | 9 / 2 | |
| 2.2.1 | 9 / 2 | |
| 2.2.0 | 9 / 2 |
v2.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.