← Home

@metamask/profile-sync-controller

npm Repository Homepage
7
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kumavismetamaskbotgudahtt

Keywords

EthereumMetaMask

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@metamask/snaps-sdk AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on config-only references, not a real risk. ai
phantom-deps phantom-dep:@metamask/snaps-utils AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on config-only references, not a real risk. ai
phantom-deps phantom-dep:immer AI (phantom-deps): Config-only reference in a monorepo; stable false positive for this package. ai
phantom-deps phantom-dep:loglevel AI (phantom-deps): Config-only reference in a monorepo; stable false positive for this package. ai

Versions (showing 7 of 7)

Version Deps Published
28.1.1 13 / 19
28.1.0 13 / 19
28.0.2 13 / 19
28.0.1 13 / 19
28.0.0 13 / 19
27.1.0 13 / 18
27.0.0 10 / 21

v28.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v28.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v27.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v27.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.