@atom8n/n8n-core
Core functionality of 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/backend-common | AI (phantom-deps): Same-org monorepo dep; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@atom8n/config | AI (phantom-deps): Same-org monorepo dep; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@atom8n/constants | AI (phantom-deps): Same-org monorepo dep; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@atom8n/decorators | AI (phantom-deps): Same-org monorepo dep; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@atom8n/n8n-workflow | AI (phantom-deps): Same-org monorepo dep; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@atom8n/client-oauth2 | AI (phantom-deps): Same-org monorepo dep; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@atom8n/di | AI (phantom-deps): Same-org monorepo dep; re-exported rather than directly imported — stable FP for this package. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): Declared dependency; used indirectly in config. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:callsites | AI (phantom-deps): Declared dependency; used indirectly in config. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Declared dependency; used indirectly in config. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:htmlparser2 | AI (phantom-deps): Declared dependency; used indirectly in config. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:xml2js | AI (phantom-deps): Declared dependency; used indirectly in config. Stable pattern for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.5.7 | 38 / 9 | |
| 2.5.6 | 38 / 9 | |
| 2.5.5 | 38 / 9 | |
| 2.5.4 | 38 / 9 | |
| 2.5.3 | 38 / 9 | |
| 2.5.2 | 38 / 9 | |
| 2.5.1 | 38 / 9 | |
| 2.5.0 | 38 / 9 | |
| 2.4.5 | 38 / 9 | |
| 2.4.4 | 38 / 9 | |
| 2.4.3 | 38 / 9 | |
| 2.4.2 | 38 / 9 | |
| 2.4.1 | 38 / 9 | |
| 2.4.0 | 38 / 9 | |
| 2.3.1 | 38 / 9 | |
| 2.3.0 | 38 / 9 | |
| 2.2.9 | 38 / 9 | |
| 2.2.8 | 38 / 9 | |
| 2.2.7 | 38 / 9 | |
| 2.2.6 | 38 / 9 | |
| 2.2.4 | 38 / 9 | |
| 2.2.3 | 38 / 9 | |
| 2.2.1 | 38 / 9 | |
| 2.2.0 | 38 / 9 |
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
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.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.