@semcore/sticky
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): Sibling package in the same Semrush intergalactic monorepo; consistently co-published with this package. | ai | |
| phantom-deps | phantom-dep:@semcore/flex-box | AI (phantom-deps): Same org scope (@semcore); declared as a runtime dependency in package.json, likely re-exported rather than directly imported. | ai | |
| provenance | no-provenance | AI (provenance): Semrush UI kit org does not publish with Sigstore provenance; consistent across all versions. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 16.1.1 | 1 / 2 | |
| 16.1.0 | 1 / 2 | |
| 3.41.0 | 2 / 2 | |
| 3.40.4 | 2 / 2 |
v16.1.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.1.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.
v3.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.