@tapjs/processinfo
A Node.js loader to track processes and which JavaScript files they load.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:node-options-to-argv | AI (dependencies): Utility dep appropriate for process-info tracking; published by trusted ecosystem author. | ai | |
| provenance | no-provenance | AI (provenance): Established high-trust publisher; absence of Sigstore attestation is not a blocker for this package. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 3.1.12 | 5 / 13 | |
| 3.1.11 | 5 / 13 | |
| 3.1.10 | 5 / 14 | |
| 3.1.9 | 5 / 14 | |
| 3.1.8 | 4 / 14 | |
| 3.1.7 | 4 / 14 | |
| 3.1.6 | 4 / 14 | |
| 3.1.5 | 4 / 14 | |
| 3.1.4 | 4 / 14 | |
| 3.1.3 | 4 / 14 | |
| 3.1.2 | 4 / 14 | |
| 3.1.1 | 4 / 13 | |
| 3.1.0 | 4 / 13 | |
| 3.0.2 | 4 / 13 | |
| 3.0.1 | 4 / 13 | |
| 3.0.0 | 4 / 13 | |
| 2.5.6 | 4 / 12 | |
| 2.5.5 | 4 / 12 | |
| 2.5.4 | 4 / 12 | |
| 2.5.3 | 4 / 12 | |
| 2.5.2 | 4 / 12 | |
| 2.5.1 | 4 / 12 | |
| 2.5.0 | 4 / 12 | |
| 2.4.1 | 4 / 12 | |
| 2.4.0 | 4 / 12 | |
| 2.3.0 | 4 / 12 | |
| 2.2.8 | 4 / 12 | |
| 2.2.7 | 4 / 12 | |
| 2.2.6 | 4 / 12 | |
| 2.2.5 | 4 / 12 | |
| 2.2.4 | 4 / 12 | |
| 2.2.3 | 4 / 12 | |
| 2.2.2 | 4 / 12 | |
| 2.2.1 | 4 / 12 | |
| 2.2.0 | 4 / 11 | |
| 2.1.5 | 4 / 11 | |
| 2.1.4 | 4 / 11 | |
| 2.1.3 | 4 / 11 | |
| 2.1.2 | 4 / 11 | |
| 2.1.1 | 4 / 11 | |
| 2.1.0 | 4 / 11 | |
| 2.0.2 | 4 / 11 | |
| 2.0.1 | 4 / 11 | |
| 2.0.0 | 4 / 11 | |
| 1.0.12 | 4 / 6 | |
| 1.0.11 | 4 / 6 | |
| 1.0.10 | 4 / 6 | |
| 1.0.9 | 4 / 6 | |
| 1.0.8 | 4 / 6 | |
| 1.0.7 | 4 / 6 | |
| 1.0.6 | 4 / 6 | |
| 1.0.5 | 3 / 6 | |
| 1.0.4 | 4 / 5 | |
| 1.0.3 | 4 / 5 | |
| 1.0.2 | 4 / 5 | |
| 1.0.1 | 4 / 5 | |
| 1.0.0 | 4 / 4 |
v3.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
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.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
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.2
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.