read-package-tree
Read the contents of node_modules.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): The iarna→zkat transition is a documented, legitimate npm team maintainer handoff for this official npm org package. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): zkat is a well-known npm core contributor; this maintainer addition is a legitimate team transition for an official npm org package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance attestation; absence is expected for this era of publishing. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 5.3.1 | 3 / 4 | |
| 5.3.0 | 3 / 4 | |
| 5.2.2 | 5 / 4 | |
| 5.2.1 | 5 / 4 | |
| 5.2.0 | 5 / 4 | |
| 5.1.6 | 5 / 4 | |
| 5.1.5 | 5 / 3 | |
| 5.1.4 | 5 / 3 | |
| 5.1.3 | 5 / 3 | |
| 5.1.2 | 5 / 2 | |
| 5.1.1 | 5 / 2 | |
| 5.1.0 | 5 / 2 | |
| 5.0.0 | 5 / 2 | |
| 4.1.0 | 5 / 2 | |
| 4.0.2 | 5 / 2 | |
| 4.0.1 | 5 / 2 | |
| 4.0.0 | 6 / 2 | |
| 3.0.0 | 5 / 2 | |
| 2.2.0 | 5 / 2 | |
| 2.0.0 | 5 / 2 | |
| 1.0.0 | 5 / 2 |
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-26. This could indicate a legitimate maintainer transition or an account compromise.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
2 findingsThis version was published by a different npm account than previous versions on 2018-04-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.