← Home

libtap

npm Repository Homepage

A Test-Anything-Protocol library for JavaScript

16
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

isaacscoreyfarrell

Keywords

asserttaptesttesting

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Signal is driven solely by isaacs being flagged as spam, which is a false positive. isaacs is the original npm creator and a core Node.js ecosystem contributor. ai
semgrep semgrep:child-process-import AI (semgrep): libtap is a TAP test runner; spawning child processes to run test suites is core, expected functionality. Stable for this package. ai
semgrep semgrep:child-process-spawn AI (semgrep): cp.spawn() in lib/spawn.js is the documented mechanism for running test subprocesses in this TAP library. Stable for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require(this.file) in lib/snapshot.js loads snapshot files during test runs — expected behavior for a test framework. Stable for this package. ai

Versions (showing 16 of 16)

Version Deps Published
1.4.1 13 / 9
1.4.0 13 / 9
1.3.0 13 / 9
1.2.2 13 / 9
1.2.1 13 / 9
1.2.0 13 / 9
1.1.4 14 / 9
1.1.3 14 / 9
1.1.2 14 / 9
1.1.1 14 / 9
1.1.0 14 / 9
1.0.1 14 / 9
1.0.0 14 / 9
0.3.0 14 / 9
0.2.0 14 / 6
0.1.0 14 / 6

v1.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

2 findings
HIGH Publisher changed: coreyfarrell → isaacs (on 2021-03-25) provenance

This version was published by a different npm account than previous versions on 2021-03-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.