@metamask/insights-example-snap
MetaMask example snap demonstrating the use of the Transaction Insights API.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@metamask/utils | AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic misfires on bundled snaps. | ai | |
| phantom-deps | phantom-dep:@metamask/snaps-sdk | AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic misfires on bundled snaps. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.2.3 | 2 / 28 | |
| 2.2.2 | 2 / 28 | |
| 2.2.1 | 2 / 28 | |
| 2.2.0 | 2 / 28 | |
| 2.1.0 | 2 / 28 | |
| 2.0.1 | 3 / 28 | |
| 2.0.0 | 3 / 28 |
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.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.