@metamask/test-snap-confirm
MetaMask Confirm Test 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
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.6.4 | 1 / 21 | |
| 4.6.3 | 1 / 21 | |
| 4.6.2 | 1 / 21 | |
| 4.6.1 | 1 / 21 | |
| 4.6.0 | 1 / 21 | |
| 4.5.0 | 1 / 21 | |
| 4.4.1 | 1 / 21 | |
| 4.4.0 | 1 / 21 | |
| 4.3.0 | 1 / 21 | |
| 4.2.0 | 1 / 21 | |
| 4.1.2 | 1 / 21 | |
| 4.1.1 | 1 / 21 | |
| 4.1.0 | 1 / 21 | |
| 4.0.2 | 1 / 21 | |
| 4.0.1 | 1 / 21 | |
| 4.0.0 | 1 / 21 |
v4.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
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 (metamaskbot) than the most recent previously approved version (ritave) on 2022-11-18, but metamaskbot 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.
v4.1.1
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 (metamaskbot) than the most recent previously approved version (ritave) on 2022-11-18, but metamaskbot 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.
v4.1.0
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 (ritave) than the most recent previously approved version (gudahtt) on 2022-11-17, but ritave 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.
v4.0.2
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 (rekmarks) than the most recent previously approved version (gudahtt) on 2022-11-11, but rekmarks 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.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.