@metamask/inpage-provider
A JavaScript Ethereum provider that connects to the wallet over a stream.
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:@types/chrome | AI (phantom-deps): Type-only package loaded by convention in browser extension context; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:webextension-polyfill-ts | AI (phantom-deps): Referenced in config files for extension polyfill; not directly imported by design. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 8.1.0 | 12 / 21 | |
| 8.0.4 | 8 / 14 | |
| 8.0.3 | 8 / 14 | |
| 8.0.2 | 8 / 14 |
v8.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gudahtt) than the most recent previously approved version (rekmarks) on 2021-01-20, but gudahtt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.