@semcore/errors
Semrush Errors 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@semcore/utils | AI (dependencies): Same org/monorepo dep (@semcore/utils); stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@semcore/typography | AI (phantom-deps): @semcore/typography is a declared runtime dep in the same org scope; phantom-dep heuristic is a false positive here. | ai | |
| dependencies | unvetted-dep:@semcore/button | AI (dependencies): Same-org sibling dependency from the Semrush intergalactic monorepo; not an external risk. | ai | |
| provenance | no-provenance | AI (provenance): Established Semrush UI kit; no provenance is consistent across all versions of this package family. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 17.1.0 | 3 / 3 | |
| 17.0.2 | 3 / 3 | |
| 17.0.1 | 3 / 3 | |
| 17.0.0 | 3 / 3 | |
| 16.2.1 | 5 / 2 | |
| 16.2.0 | 5 / 2 | |
| 16.1.7 | 5 / 2 | |
| 4.48.0 | 6 / 2 |
v17.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.48.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 (semrushinc) than the most recent previously approved version (uikit-team) on 2026-05-13, but semrushinc 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.