@knapsack/babel-config
Babel config and deps.
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:@babel/cli | AI (phantom-deps): Babel framework package loaded by convention in config packages. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Babel framework package loaded by convention in config packages. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Babel framework package loaded by convention in config packages. | ai | |
| phantom-deps | phantom-dep:@knapsack/file-utils | AI (phantom-deps): Same-org scoped package; stable pattern for monorepo configs. | ai |
Versions (showing 8 of 118)
| Version | Deps | Published |
|---|---|---|
| 4.80.4 | 15 / 4 | |
| 4.80.3 | 15 / 4 | |
| 4.80.2 | 15 / 4 | |
| 4.80.1 | 15 / 4 | |
| 4.80.0 | 15 / 4 | |
| 4.79.2 | 15 / 4 | |
| 4.79.1 | 15 / 4 | |
| 4.79.0 | 15 / 4 |
v4.80.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.79.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.79.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.