@knapsack/test-ava
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:@ava/typescript | AI (dependencies): @ava/typescript is the official AVA TypeScript plugin; expected dependency for this AVA config wrapper package. | ai | |
| provenance | no-provenance | AI (provenance): Established knapsack monorepo package; provenance not enabled but no other risk signals present. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Empty description is a known pattern for this monorepo package; not indicative of malice. | ai | |
| phantom-deps | phantom-dep:@ava/typescript | AI (phantom-deps): AVA plugin loaded by convention via ava config, not directly imported. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-runtime | AI (phantom-deps): Babel plugin loaded by framework convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:@babel/preset-env | AI (phantom-deps): Babel preset loaded by framework convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:@babel/preset-typescript | AI (phantom-deps): Babel preset loaded by framework convention, not directly imported. | ai |
Versions (showing 51 of 67)
| Version | Deps | Published |
|---|---|---|
| 4.92.24 | 8 / 4 | |
| 4.92.23 | 8 / 4 | |
| 4.92.21 | 8 / 4 | |
| 4.92.20 | 8 / 4 | |
| 4.92.19 | 8 / 4 | |
| 4.92.18 | 8 / 4 | |
| 4.92.17 | 8 / 4 | |
| 4.92.13 | 8 / 4 | |
| 4.92.11 | 8 / 4 | |
| 4.92.8 | 8 / 4 | |
| 4.92.7 | 8 / 4 | |
| 4.92.6 | 8 / 4 | |
| 4.92.3 | 8 / 4 | |
| 4.92.2 | 8 / 4 | |
| 4.92.1 | 8 / 4 | |
| 4.92.0 | 8 / 4 | |
| 4.91.0 | 8 / 4 | |
| 4.90.0 | 8 / 4 | |
| 4.89.13 | 8 / 4 | |
| 4.89.11 | 8 / 4 | |
| 4.89.10 | 8 / 4 | |
| 4.89.8 | 8 / 4 | |
| 4.89.7 | 8 / 4 | |
| 4.89.6 | 8 / 4 | |
| 4.89.3 | 8 / 4 | |
| 4.89.1 | 8 / 4 | |
| 4.89.0 | 8 / 4 | |
| 4.88.0 | 8 / 4 | |
| 4.87.9 | 8 / 4 | |
| 4.87.6 | 8 / 4 | |
| 4.87.4 | 8 / 4 | |
| 4.87.3 | 8 / 4 | |
| 4.87.0 | 8 / 4 | |
| 4.86.6 | 8 / 4 | |
| 4.86.5 | 8 / 4 | |
| 4.86.3 | 8 / 4 | |
| 4.86.2 | 8 / 4 | |
| 4.86.0 | 8 / 4 | |
| 4.85.8 | 8 / 4 | |
| 4.85.7 | 8 / 4 | |
| 4.85.4 | 8 / 4 | |
| 4.85.3 | 8 / 4 | |
| 4.85.1 | 8 / 4 | |
| 4.85.0 | 8 / 4 | |
| 4.84.0 | 8 / 4 | |
| 4.83.0 | 8 / 4 | |
| 4.82.3 | 8 / 4 | |
| 4.82.2 | 8 / 4 | |
| 4.82.1 | 8 / 4 | |
| 4.81.4 | 8 / 4 | |
| 4.81.3 | 8 / 4 |
v4.92.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.23
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.90.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.89.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.88.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.86.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.84.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.81.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.81.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.