knip
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Major version bump naturally adds many files; no obfuscation or suspicious content. | ai | |
| provenance | missing-githead | AI (provenance): Major version bump (v5→v6) with publish environment change; trusted long-standing publisher. | ai | |
| provenance | no-provenance | AI (provenance): Knip has never had provenance; low-risk for this well-established package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): False positive; knip publishes frequently (581 versions). Publisher webpro is well-established. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): knip is a well-established independent tool with 6.7M weekly downloads; not a typosquat of knex. | ai | |
| dependencies | unvetted-dep:formatly | AI (dependencies): formatly is authored by the same webpro-nl publisher; fits knip's output formatting use case. | ai | |
| dependencies | unvetted-dep:unbash | AI (dependencies): unbash is authored by the same webpro-nl publisher; fits knip's shell-parsing use case. | ai |
Versions (showing 51 of 82)
| Version | Deps | Published |
|---|---|---|
| 6.17.1 | 13 / 8 | |
| 6.17.0 | 13 / 8 | |
| 6.16.1 | 13 / 8 | |
| 6.16.0 | 13 / 8 | |
| 6.15.0 | 14 / 9 | |
| 6.14.2 | 14 / 10 | |
| 6.14.1 | 14 / 10 | |
| 6.14.0 | 14 / 10 | |
| 6.13.1 | 14 / 10 | |
| 6.13.0 | 14 / 10 | |
| 6.12.2 | 14 / 10 | |
| 6.12.1 | 14 / 10 | |
| 6.12.0 | 14 / 10 | |
| 6.11.0 | 14 / 10 | |
| 6.10.0 | 14 / 10 | |
| 6.9.0 | 14 / 10 | |
| 6.8.0 | 14 / 10 | |
| 6.7.0 | 14 / 10 | |
| 6.6.3 | 14 / 10 | |
| 6.6.2 | 14 / 10 | |
| 6.6.1 | 14 / 10 | |
| 6.6.0 | 14 / 10 | |
| 6.5.0 | 15 / 10 | |
| 6.4.1 | 15 / 11 | |
| 6.4.0 | 15 / 11 | |
| 6.3.1 | 15 / 11 | |
| 6.3.0 | 15 / 11 | |
| 6.2.0 | 15 / 11 | |
| 6.1.1 | 15 / 11 | |
| 6.1.0 | 15 / 11 | |
| 6.0.6 | 15 / 11 | |
| 6.0.5 | 15 / 11 | |
| 6.0.4 | 15 / 11 | |
| 6.0.3 | 15 / 11 | |
| 6.0.2 | 15 / 11 | |
| 6.0.1 | 15 / 11 | |
| 6.0.0 | 15 / 11 | |
| 5.88.1 | 13 / 11 | |
| 5.88.0 | 13 / 11 | |
| 5.87.0 | 13 / 11 | |
| 5.86.0 | 13 / 11 | |
| 5.85.0 | 12 / 11 | |
| 5.84.1 | 12 / 11 | |
| 5.84.0 | 12 / 11 | |
| 5.83.1 | 12 / 11 | |
| 5.83.0 | 12 / 11 | |
| 5.82.1 | 12 / 11 | |
| 5.82.0 | 12 / 11 | |
| 5.81.0 | 12 / 11 | |
| 5.80.2 | 12 / 11 | |
| 5.80.1 | 12 / 11 |
v6.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.88.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.88.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.87.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.86.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.85.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.84.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.84.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.83.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.83.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.82.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.82.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.81.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.80.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.80.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webpro.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.