@knapsack/creator-utils
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:fs-extra | AI (phantom-deps): fs-extra is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:handlebars | AI (phantom-deps): handlebars is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 65)
| Version | Deps | Published |
|---|---|---|
| 4.92.24 | 11 / 8 | |
| 4.92.23 | 11 / 8 | |
| 4.92.22 | 11 / 8 | |
| 4.92.21 | 11 / 8 | |
| 4.92.20 | 11 / 8 | |
| 4.92.19 | 11 / 8 | |
| 4.92.18 | 11 / 8 | |
| 4.92.17 | 11 / 8 | |
| 4.92.14 | 11 / 8 | |
| 4.92.13 | 11 / 8 | |
| 4.92.12 | 11 / 8 | |
| 4.92.7 | 11 / 8 | |
| 4.92.2 | 11 / 8 | |
| 4.92.1 | 11 / 8 | |
| 4.92.0 | 11 / 8 | |
| 4.89.13 | 11 / 8 | |
| 4.89.11 | 11 / 8 | |
| 4.89.10 | 11 / 8 | |
| 4.89.9 | 11 / 8 | |
| 4.89.8 | 11 / 8 | |
| 4.89.5 | 11 / 8 | |
| 4.89.3 | 11 / 8 | |
| 4.89.2 | 11 / 8 | |
| 4.87.9 | 11 / 8 | |
| 4.87.7 | 11 / 8 | |
| 4.87.6 | 11 / 8 | |
| 4.87.1 | 11 / 8 | |
| 4.87.0 | 11 / 8 | |
| 4.86.8 | 11 / 8 | |
| 4.86.6 | 11 / 8 | |
| 4.86.5 | 11 / 8 | |
| 4.86.3 | 11 / 8 | |
| 4.86.2 | 11 / 8 | |
| 4.86.1 | 11 / 8 | |
| 4.85.9 | 11 / 8 | |
| 4.85.7 | 11 / 8 | |
| 4.85.6 | 11 / 8 | |
| 4.85.5 | 11 / 8 | |
| 4.85.3 | 11 / 8 | |
| 4.85.1 | 11 / 8 | |
| 4.85.0 | 11 / 8 | |
| 4.83.0 | 11 / 8 | |
| 4.82.3 | 11 / 8 | |
| 4.82.2 | 11 / 8 | |
| 4.82.1 | 11 / 8 | |
| 4.81.5 | 11 / 8 | |
| 4.81.3 | 11 / 8 | |
| 4.81.2 | 11 / 8 | |
| 4.80.20 | 11 / 8 | |
| 4.80.19 | 11 / 8 | |
| 4.80.18 | 11 / 8 |
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.89.13
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.5
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.87.9
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.87.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.86.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.85.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.81.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.81.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.81.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.80.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.80.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.80.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.