@semcore/notice-global
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): Internal @semcore/* sibling dependency; expected pattern for this component family. | ai | |
| dependencies | unvetted-dep:@semcore/button | AI (dependencies): Internal @semcore/* sibling dependency; expected pattern for this component family. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from semrushinc to uikit-team matches package author field and Semrush org repo; consistent with org account migration. | ai | |
| provenance | no-provenance | AI (provenance): Semrush intergalactic monorepo does not publish with Sigstore provenance; stable pattern across all versions. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 16.2.1 | 4 / 2 | |
| 16.2.0 | 4 / 2 | |
| 16.1.13 | 4 / 2 | |
| 16.1.12 | 4 / 2 | |
| 2.63.0 | 5 / 2 | |
| 2.62.2 | 5 / 2 |
v16.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.