test-runner
Fully-featured, lightweight command-line test runner
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is the core mechanism for a test runner CLI to load user test modules — intentional and expected behavior for this package. | ai | |
| phantom-deps | phantom-dep:file-set | AI (phantom-deps): CLI package uses deps in bin/lib scripts not just index.js; phantom-dep analyzer only checks direct imports in index.js, producing false positives for this package. | ai | |
| phantom-deps | phantom-dep:walk-back | AI (phantom-deps): Same as above — CLI package uses deps across bin/lib, not just index.js. | ai | |
| phantom-deps | phantom-dep:reduce-flatten | AI (phantom-deps): Same as above — CLI package uses deps across bin/lib, not just index.js. | ai | |
| phantom-deps | phantom-dep:test-runner-core | AI (phantom-deps): Same as above — CLI package uses deps across bin/lib, not just index.js. | ai | |
| phantom-deps | phantom-dep:command-line-args | AI (phantom-deps): Same as above — CLI package uses deps across bin/lib, not just index.js. | ai | |
| phantom-deps | phantom-dep:command-line-usage | AI (phantom-deps): Same as above — CLI package uses deps across bin/lib, not just index.js. | ai | |
| phantom-deps | phantom-dep:@test-runner/default-view | AI (phantom-deps): Same as above — CLI package uses deps across bin/lib, not just index.js. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.11.1 | 11 / 2 | |
| 0.11.0 | 11 / 2 | |
| 0.10.1 | 11 / 3 | |
| 0.10.0 | 11 / 3 | |
| 0.9.8 | 11 / 3 | |
| 0.9.7 | 11 / 5 | |
| 0.9.6 | 11 / 5 | |
| 0.7.0 | 9 / 1 | |
| 0.6.3 | 9 / 1 | |
| 0.5.1 | 6 / 1 | |
| 0.5.0 | 6 / 1 | |
| 0.4.1 | 6 / 1 | |
| 0.4.0 | 6 / 1 | |
| 0.3.0 | 7 / 3 | |
| 0.2.5 | 7 / 3 | |
| 0.2.4 | 8 / 3 | |
| 0.2.3 | 8 / 3 | |
| 0.2.2 | 8 / 3 | |
| 0.2.1 | 8 / 3 | |
| 0.2.0 | 8 / 3 | |
| 0.1.13 | 6 / 1 | |
| 0.1.12 | 6 / 1 | |
| 0.1.11 | 6 / 1 | |
| 0.1.10 | 6 / 1 | |
| 0.1.9 | 5 / 1 | |
| 0.1.8 | 5 / 1 | |
| 0.1.7 | 5 / 1 | |
| 0.1.6 | 5 / 1 | |
| 0.1.5 | 5 / 1 | |
| 0.1.4 | 5 / 1 | |
| 0.1.3 | 5 / 1 | |
| 0.1.2 | 5 / 1 | |
| 0.1.1 | 5 / 1 | |
| 0.1.0 | 4 / 0 |
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.