ethjs-query
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:babel-runtime | AI (phantom-deps): babel-runtime is declared in package.json dependencies; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.3.8 | 4 / 47 | |
| 0.0.5 | 2 / 17 | |
| 0.0.2 | 2 / 15 | |
| 0.0.1 | 2 / 15 |
v0.0.5
2 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.