@knapsack/esbuild-tool
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@knapsack/creator-utils | AI (dependencies): Same-org monorepo sibling dependency; version-locked to match this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal tooling package in a large monorepo; sparse README/metadata is expected for internal packages. | ai |
Versions (showing 14 of 119)
| Version | Deps | Published |
|---|---|---|
| 4.80.10 | 3 / 5 | |
| 4.80.9 | 3 / 5 | |
| 4.80.8 | 3 / 5 | |
| 4.80.7 | 3 / 5 | |
| 4.80.6 | 3 / 5 | |
| 4.80.5 | 3 / 5 | |
| 4.80.4 | 3 / 5 | |
| 4.80.3 | 3 / 5 | |
| 4.80.2 | 3 / 5 | |
| 4.80.1 | 3 / 5 | |
| 4.80.0 | 3 / 5 | |
| 4.79.2 | 3 / 5 | |
| 4.79.1 | 3 / 5 | |
| 4.79.0 | 3 / 5 |
v4.80.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.