tap-runner
A module for running all the tests in a directory
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:yamlish | AI (phantom-deps): yamlish is declared in package.json and legitimately used; phantom-dep false positive for properly declared dependencies. | ai | |
| phantom-deps | phantom-dep:tap-results | AI (phantom-deps): tap-results is declared in package.json and legitimately used; phantom-dep false positive for properly declared dependencies. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): tap-runner is a test runner; spawning child processes is its core function. child_process use is expected and benign for this package. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): spawn() is the mechanism by which tap-runner executes test files — fundamental to its purpose, not a security concern. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.0.7 | 7 / 0 | |
| 0.0.6 | 7 / 0 | |
| 0.0.5 | 7 / 0 | |
| 0.0.4 | 7 / 0 | |
| 0.0.3 | 7 / 0 | |
| 0.0.2 | 7 / 0 | |
| 0.0.1 | 6 / 0 |
v0.0.7
2 findingsMatched 4 signal(s), weighted score 7: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: isaacs. • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_KEYWORDS] No keywords declared. • [S_TINY_PAYLOAD] Tiny payload: 1 code file(s), 3772 bytes total.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.