@knapsack/update
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:prompts | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@knapsack/creator-utils | AI (phantom-deps): Same-org scoped dependency; expected in monorepo. | ai | |
| phantom-deps | phantom-dep:@knapsack/design-token-utils | AI (phantom-deps): Same-org scoped dependency; expected in monorepo. | ai |
Versions (showing 7 of 117)
| Version | Deps | Published |
|---|---|---|
| 4.80.3 | 13 / 12 | |
| 4.80.2 | 13 / 12 | |
| 4.80.1 | 13 / 12 | |
| 4.80.0 | 13 / 12 | |
| 4.79.2 | 12 / 11 | |
| 4.79.1 | 12 / 11 | |
| 4.79.0 | 12 / 11 |
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.