@metamask/browserify-example-snap
MetaMask example snap demonstrating how to use Browserify to bundle a snap.
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/snaps-sdk | AI (phantom-deps): Snap bundles may not have direct imports detectable by static analysis; same-org dep declared in package.json. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Example/demo package in a monorepo; minimal README and no keywords are expected for this type of package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 1 / 29 | |
| 2.1.2 | 1 / 29 | |
| 2.1.1 | 2 / 29 | |
| 2.1.0 | 2 / 29 | |
| 2.0.1 | 2 / 29 | |
| 2.0.0 | 2 / 29 |
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.