@knapsack/monorepo-tools
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:syncpack | AI (phantom-deps): syncpack is a CLI tool used in config/scripts, not imported directly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@auto-it/npm | AI (phantom-deps): auto-it/npm is a release plugin used via config, not directly imported; stable false positive for this package. | ai |
Versions (showing 15 of 118)
| Version | Deps | Published |
|---|---|---|
| 4.80.11 | 5 / 5 | |
| 4.80.10 | 5 / 5 | |
| 4.80.9 | 5 / 5 | |
| 4.80.8 | 5 / 5 | |
| 4.80.7 | 5 / 5 | |
| 4.80.6 | 5 / 5 | |
| 4.80.5 | 5 / 5 | |
| 4.80.4 | 5 / 5 | |
| 4.80.3 | 5 / 5 | |
| 4.80.2 | 5 / 5 | |
| 4.80.1 | 5 / 5 | |
| 4.80.0 | 5 / 5 | |
| 4.79.2 | 5 / 5 | |
| 4.79.1 | 5 / 5 | |
| 4.79.0 | 5 / 5 |
v4.80.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.