@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 51 of 108)
| Version | Deps | Published |
|---|---|---|
| 4.93.0 | 3 / 5 | |
| 4.92.24 | 3 / 5 | |
| 4.92.23 | 3 / 5 | |
| 4.92.22 | 3 / 5 | |
| 4.92.21 | 3 / 5 | |
| 4.92.20 | 3 / 5 | |
| 4.92.19 | 3 / 5 | |
| 4.92.18 | 3 / 5 | |
| 4.92.17 | 3 / 5 | |
| 4.92.16 | 3 / 5 | |
| 4.92.15 | 3 / 5 | |
| 4.92.14 | 3 / 5 | |
| 4.92.13 | 3 / 5 | |
| 4.92.12 | 3 / 5 | |
| 4.92.11 | 3 / 5 | |
| 4.92.10 | 3 / 5 | |
| 4.92.9 | 3 / 5 | |
| 4.92.8 | 3 / 5 | |
| 4.92.7 | 3 / 5 | |
| 4.92.6 | 3 / 5 | |
| 4.92.5 | 3 / 5 | |
| 4.92.4 | 3 / 5 | |
| 4.92.3 | 3 / 5 | |
| 4.92.2 | 3 / 5 | |
| 4.92.1 | 3 / 5 | |
| 4.92.0 | 3 / 5 | |
| 4.91.0 | 3 / 5 | |
| 4.90.0 | 3 / 5 | |
| 4.89.13 | 3 / 5 | |
| 4.89.12 | 3 / 5 | |
| 4.89.11 | 3 / 5 | |
| 4.89.10 | 3 / 5 | |
| 4.89.9 | 3 / 5 | |
| 4.89.8 | 3 / 5 | |
| 4.89.7 | 3 / 5 | |
| 4.89.6 | 3 / 5 | |
| 4.89.5 | 3 / 5 | |
| 4.89.4 | 3 / 5 | |
| 4.89.3 | 3 / 5 | |
| 4.89.2 | 3 / 5 | |
| 4.89.1 | 3 / 5 | |
| 4.89.0 | 3 / 5 | |
| 4.88.0 | 3 / 5 | |
| 4.87.9 | 3 / 5 | |
| 4.87.8 | 3 / 5 | |
| 4.87.7 | 3 / 5 | |
| 4.87.6 | 3 / 5 | |
| 4.87.5 | 3 / 5 | |
| 4.87.4 | 3 / 5 | |
| 4.87.3 | 3 / 5 | |
| 4.87.2 | 3 / 5 |
v4.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.87.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.