← Home

@tapjs/run

Command-line interface for the node-tap runner

69
Versions
BlueOak-1.0.0
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

ljharbisaacs

Keywords

tapjsrunnercli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established package by isaacs; lack of provenance is consistent across all versions and not a meaningful risk signal here. ai
bogus-package bogus-package AI (bogus-package): isaacs is the creator of npm/node-tap; SPAM-FLAGGED is a false positive for this well-known author. Short README is expected for a monorepo sub-package. ai
phantom-deps phantom-dep:tap-parser AI (phantom-deps): tap-parser is a declared dep used indirectly via config in this monorepo sub-package; stable pattern across versions. ai
phantom-deps phantom-dep:path-scurry AI (phantom-deps): path-scurry is a declared dep used indirectly via config in this monorepo sub-package; stable pattern across versions. ai

Versions (showing 69 of 69)

Version Deps Published
4.5.7 28 / 0
4.5.6 28 / 0
4.5.5 28 / 0
4.5.4 28 / 0
4.5.3 28 / 0
4.3.0 28 / 0
4.2.0 27 / 0
4.1.0 27 / 0
4.0.8 27 / 0
4.0.7 27 / 0
4.0.6 27 / 0
4.0.5 27 / 0
4.0.4 27 / 0
4.0.3 27 / 0
4.0.2 27 / 0
4.0.1 27 / 0
4.0.0 27 / 0
3.0.3 26 / 0
3.0.2 26 / 0
3.0.1 26 / 0
3.0.0 26 / 0
2.1.7 26 / 0
2.1.6 26 / 0
2.1.5 26 / 0
2.1.4 26 / 0
2.1.3 26 / 0
2.1.2 26 / 0
2.1.1 26 / 0
2.1.0 26 / 0
2.0.2 26 / 0
2.0.1 26 / 0
2.0.0 26 / 0
1.5.4 26 / 0
1.5.3 26 / 0
1.5.2 26 / 0
1.5.1 26 / 0
1.5.0 26 / 0
1.4.16 26 / 0
1.4.15 26 / 0
1.4.14 26 / 0
1.4.13 26 / 0
1.4.12 26 / 0
1.4.11 26 / 0
1.4.10 26 / 0
1.4.9 26 / 0
1.4.8 26 / 0
1.4.7 26 / 0
1.4.6 26 / 0
1.4.5 26 / 0
1.4.4 26 / 0
1.4.3 26 / 0
1.4.2 26 / 0
1.4.1 26 / 0
1.4.0 26 / 0
1.3.3 26 / 0
1.3.2 26 / 0
1.3.1 26 / 0
1.3.0 26 / 0
1.2.0 26 / 0
1.1.4 26 / 0
1.1.3 26 / 0
1.1.2 26 / 0
1.1.1 26 / 0
1.1.0 26 / 0
1.0.4 26 / 0
1.0.3 26 / 0
1.0.2 26 / 0
1.0.1 26 / 0
1.0.0 26 / 0

v4.5.7

1 finding
INFO No provenance attestation provenance

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

v4.5.6

1 finding
LOW No provenance attestation provenance

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

v4.5.5

1 finding
LOW No provenance attestation provenance

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

v4.5.4

1 finding
LOW No provenance attestation provenance

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

v4.5.3

1 finding
LOW No provenance attestation provenance

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

v4.3.0

1 finding
LOW No provenance attestation provenance

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

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.8

1 finding
LOW No provenance attestation provenance

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

v4.0.7

1 finding
LOW No provenance attestation provenance

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

v4.0.6

1 finding
LOW No provenance attestation provenance

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

v4.0.5

1 finding
LOW No provenance attestation provenance

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

v4.0.4

1 finding
LOW No provenance attestation provenance

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

v4.0.3

1 finding
LOW No provenance attestation provenance

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

v4.0.2

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.1.7

1 finding
LOW No provenance attestation provenance

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

v2.1.6

1 finding
LOW No provenance attestation provenance

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

v2.1.5

1 finding
LOW No provenance attestation provenance

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

v2.1.4

1 finding
LOW No provenance attestation provenance

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

v2.1.3

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.5.4

1 finding
LOW No provenance attestation provenance

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

v1.5.3

1 finding
LOW No provenance attestation provenance

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