@atom8n/ai-workflow-builder
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/backend-common | AI (phantom-deps): Same org-scope monorepo package; phantom-dep heuristic unreliable for workspace deps. | ai | |
| phantom-deps | phantom-dep:@atom8n/di | AI (phantom-deps): Same org-scope monorepo package; phantom-dep heuristic unreliable for workspace deps. | ai | |
| phantom-deps | phantom-dep:@atom8n/utils | AI (phantom-deps): Same org-scope monorepo package; phantom-dep heuristic unreliable for workspace deps. | ai | |
| phantom-deps | phantom-dep:@atom8n/config | AI (phantom-deps): Same org-scope monorepo package; phantom-dep heuristic unreliable for workspace deps. | ai | |
| phantom-deps | phantom-dep:@atom8n/n8n-workflow | AI (phantom-deps): Same org-scope monorepo package; phantom-dep heuristic unreliable for workspace deps. | ai | |
| phantom-deps | phantom-dep:csv-parse | AI (phantom-deps): Declared as runtime dep; likely used transitively or in config-driven code paths. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Declared as runtime dep; likely used transitively or in config-driven code paths. | ai | |
| phantom-deps | phantom-dep:@n8n/config | AI (phantom-deps): Remapped to @atom8n/config; phantom-dep heuristic likely misses the npm alias resolution. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal/forked n8n package; missing metadata is consistent across the atom8n namespace, not a spam indicator. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.5.7 | 15 / 7 | |
| 1.5.5 | 15 / 7 | |
| 1.4.0 | 15 / 7 | |
| 1.2.5 | 15 / 7 |
v1.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.