@atom8n/create-node
Official CLI to create new community nodes for n8n
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atom8n/node-cli | AI (phantom-deps): CLI delegates to @atom8n/node-cli via resolved bin path, not a direct import; stable FP for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool that delegates to n8n-node binary via spawnSync; expected pattern for a CLI wrapper. | ai | |
| phantom-deps | phantom-dep:@n8n/node-cli | AI (phantom-deps): Declared as npm alias to @atom8n/node-cli; phantom-dep heuristic doesn't resolve npm aliases correctly. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.19.7 | 1 / 1 | |
| 0.19.6 | 1 / 1 | |
| 0.19.5 | 1 / 1 | |
| 0.19.4 | 1 / 1 | |
| 0.19.3 | 1 / 1 | |
| 0.19.2 | 1 / 1 | |
| 0.19.1 | 1 / 1 | |
| 0.19.0 | 1 / 1 | |
| 0.18.3 | 1 / 1 | |
| 0.18.2 | 1 / 1 | |
| 0.18.1 | 1 / 1 | |
| 0.18.0 | 1 / 1 | |
| 0.17.0 | 1 / 1 | |
| 0.16.9 | 1 / 1 | |
| 0.16.8 | 1 / 1 | |
| 0.16.7 | 1 / 1 | |
| 0.16.6 | 1 / 1 | |
| 0.16.4 | 1 / 1 | |
| 0.16.3 | 1 / 1 | |
| 0.16.2 | 1 / 1 | |
| 0.16.1 | 1 / 1 | |
| 0.16.0 | 1 / 1 |
v0.19.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.