← Home

@material/mwc-select

npm Repository Homepage
2
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

yefimabhiomkarazakusbicknellrmaterial-adminaprigoginpatrickrodeeaomarksemarquezallanchenesgonzalezasynclizcandysonyassuareztaylorv

Keywords

material designweb componentsselect

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Google MWC team transition; new publisher emarquez is part of the same org. ai
maintainer-change maintainer-added AI (maintainer-change): Org-level maintainer rotation for Google MWC project. ai
maintainer-change maintainer-removed AI (maintainer-change): Org-level maintainer rotation for Google MWC project. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy explained by Google MWC team transition and lit v2 migration effort. ai
publish-pattern new-deps-added AI (publish-pattern): lit replaces lit-element+lit-html; canonical upstream migration, not a supply-chain addition. ai

Versions (showing 2 of 2)

Version Deps Published
0.27.0 14 / 1
0.22.1 15 / 1

v0.27.0

2 findings
HIGH Publisher changed: aomarks → emarquez (on 2022-08-12) provenance

This version was published by a different npm account than previous versions on 2022-08-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.22.1

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.