← Home

@semcore/portal

npm Repository Homepage
4
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

semrushincuikit-team

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@semcore/utils AI (dependencies): @semcore/utils is a first-party Semrush UI kit utility package from the same org/repo; stable false positive for this package family. ai
provenance publisher-changed AI (provenance): Transition from semrushinc to uikit-team is consistent with Semrush org restructuring; repo/author email confirm same org. ai
provenance no-provenance AI (provenance): Long-established Semrush UI kit package; lack of provenance is consistent across all versions and not a risk indicator here. ai

Versions (showing 4 of 4)

Version Deps Published
16.1.1 0 / 0
16.1.0 0 / 0
3.42.0 1 / 3
3.41.4 1 / 3

v16.1.1

2 findings
HIGH Publisher changed: semrushinc → uikit-team (on 2026-05-13) provenance

This 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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v16.1.0

2 findings
HIGH Publisher changed: semrushinc → uikit-team (on 2026-05-13) provenance

This 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.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.42.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.41.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.