@tapjs/core
pluggable core of node-tap
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
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 4.5.8 | 12 / 0 | |
| 4.5.7 | 12 / 0 | |
| 4.5.6 | 12 / 0 | |
| 4.5.5 | 12 / 0 | |
| 4.5.4 | 12 / 0 | |
| 4.5.3 | 12 / 0 | |
| 4.5.2 | 12 / 0 | |
| 4.5.1 | 12 / 0 | |
| 4.5.0 | 12 / 0 | |
| 4.4.1 | 12 / 0 | |
| 4.4.0 | 12 / 0 | |
| 4.3.0 | 12 / 0 | |
| 4.2.0 | 12 / 0 | |
| 4.1.0 | 12 / 0 | |
| 4.0.7 | 12 / 0 | |
| 4.0.6 | 12 / 0 | |
| 4.0.5 | 12 / 0 | |
| 4.0.4 | 12 / 0 | |
| 4.0.3 | 12 / 0 | |
| 4.0.2 | 12 / 0 | |
| 4.0.1 | 12 / 0 | |
| 4.0.0 | 12 / 0 | |
| 3.0.3 | 12 / 0 | |
| 3.0.2 | 12 / 0 | |
| 3.0.1 | 12 / 0 | |
| 3.0.0 | 12 / 0 | |
| 2.1.6 | 12 / 0 | |
| 2.1.5 | 12 / 0 | |
| 2.1.4 | 12 / 0 | |
| 2.1.3 | 12 / 0 | |
| 2.1.2 | 12 / 0 | |
| 2.1.1 | 12 / 0 | |
| 2.1.0 | 12 / 0 | |
| 2.0.1 | 12 / 0 | |
| 2.0.0 | 12 / 0 | |
| 1.5.4 | 12 / 0 | |
| 1.5.3 | 12 / 0 | |
| 1.5.2 | 12 / 0 | |
| 1.5.1 | 12 / 0 | |
| 1.5.0 | 12 / 0 | |
| 1.4.6 | 12 / 0 | |
| 1.4.5 | 12 / 0 | |
| 1.4.4 | 12 / 0 | |
| 1.4.3 | 12 / 0 | |
| 1.4.2 | 12 / 0 | |
| 1.4.1 | 12 / 0 | |
| 1.4.0 | 12 / 0 | |
| 1.3.10 | 12 / 0 | |
| 1.3.9 | 12 / 0 | |
| 1.3.8 | 12 / 0 | |
| 1.3.7 | 12 / 0 |
v4.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.