@metamask/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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:lib/tests/test.index.js | AI (source-diff): Hex EVM bytecode test fixture, not an encoded payload. | ai | |
| source-diff | encoded-string-file:src/tests/test.index.js | AI (source-diff): Hex EVM bytecode test fixture, not an encoded payload. | ai | |
| phantom-deps | phantom-dep:babel-runtime | AI (phantom-deps): Standard Babel helper runtime used implicitly by babel-transformed output. | ai | |
| provenance | no-provenance | AI (provenance): Established MetaMask package predating widespread provenance adoption; low risk without it. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 3 / 44 | |
| 0.7.0 | 3 / 44 | |
| 0.6.0 | 3 / 44 | |
| 0.5.3 | 4 / 46 | |
| 0.5.2 | 4 / 46 | |
| 0.5.1 | 4 / 46 | |
| 0.5.0 | 4 / 45 | |
| 0.4.0 | 4 / 45 |
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
3 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.