@semcore/core
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:@phytonmk/nano-css | AI (dependencies): Scoped nano-css fork used intentionally by this package for CSS-in-JS; stable dependency for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @semcore/core is Semrush's official scoped UI kit package, not a typosquat of cors. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 17.0.1 | 5 / 6 | |
| 17.0.0 | 5 / 6 | |
| 16.6.2 | 5 / 6 | |
| 16.5.2 | 5 / 6 | |
| 2.40.0 | 1 / 2 | |
| 2.39.4 | 1 / 2 |
v17.0.1
2 findingsPackage name '@semcore/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.0
2 findingsPackage name '@semcore/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.6.2
2 findingsPackage 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-27, 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.5.2
2 findingsPackage name '@semcore/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.40.0
2 findingsPackage name '@semcore/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.