@metamask/multichain-account-service
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@metamask/key-tree | AI (phantom-deps): Same-org dep declared in package.json; phantom-dep heuristic false positive. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): MetaMask org routine maintainer rotation; metamaskbot publisher has 195 approved packages and no rejections. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is listed as a runtime dep in package.json; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@metamask/base-controller | AI (phantom-deps): Same-org dependency; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:@metamask/eth-snap-keyring | AI (phantom-deps): Same-org dependency; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:@metamask/superstruct | AI (phantom-deps): Same-org dependency; likely re-exported or used transitively in monorepo. | ai | |
| phantom-deps | phantom-dep:@metamask/keyring-utils | AI (phantom-deps): Same-org dependency; likely re-exported or used transitively in monorepo. | ai | |
| provenance | no-provenance | AI (provenance): MetaMask core packages consistently lack Sigstore provenance; stable false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 10.0.2 | 19 / 17 | |
| 10.0.1 | 19 / 17 | |
| 10.0.0 | 19 / 17 | |
| 9.0.0 | 18 / 17 | |
| 8.0.1 | 18 / 17 | |
| 8.0.0 | 18 / 17 | |
| 7.1.0 | 18 / 16 | |
| 7.0.0 | 18 / 15 | |
| 6.0.0 | 18 / 15 | |
| 5.1.0 | 18 / 15 | |
| 5.0.0 | 18 / 15 | |
| 4.1.0 | 18 / 15 | |
| 4.0.1 | 18 / 15 | |
| 4.0.0 | 14 / 19 | |
| 3.0.0 | 14 / 19 | |
| 2.1.0 | 14 / 18 | |
| 2.0.1 | 14 / 17 |
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.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.
v7.1.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.
v7.0.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.
v6.0.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.
v5.1.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.
v5.0.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.
v4.1.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.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.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.
v3.0.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.
v2.1.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.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.