@semcore/button
Semrush Button Component
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Semrush intergalactic monorepo consistently publishes without Sigstore provenance; stable pattern across all versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 17.2.0 | 3 / 4 | |
| 17.1.0 | 3 / 4 | |
| 17.0.1 | 3 / 4 | |
| 17.0.0 | 3 / 4 | |
| 16.1.1 | 4 / 4 | |
| 16.1.0 | 4 / 4 | |
| 5.44.0 | 5 / 3 |
v17.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (uikit-team) than the most recent previously approved version (semrushinc) on 2026-05-14, but uikit-team 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.
v17.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.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.
v16.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (uikit-team) than the most recent previously approved version (semrushinc) on 2026-05-13, but uikit-team 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.
v16.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (uikit-team) than the most recent previously approved version (semrushinc) on 2026-05-13, but uikit-team 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.
v5.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.