← Home

@semcore/notice-bubble

npm Repository Homepage

Semrush NoticeBubble Component

10
Versions
MIT
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
publish-pattern new-deps-added AI (publish-pattern): All added deps are first-party @semcore/* packages from the same Semrush UI-kit monorepo; not a supply-chain risk. ai
phantom-deps phantom-dep:@semcore/portal AI (phantom-deps): Same-org monorepo dep; used transitively, not a direct import concern. ai
phantom-deps phantom-dep:@semcore/flex-box AI (phantom-deps): Same-org monorepo dep; used transitively, not a direct import concern. ai
phantom-deps phantom-dep:@semcore/animation AI (phantom-deps): Same-org @semcore scope dependency; stable false positive for this package family. ai
dependencies unvetted-dep:@semcore/button AI (dependencies): Same-monorepo sibling dependency from the Semrush intergalactic UI kit; not an independent risk. ai

Versions (showing 10 of 10)

Version Deps Published
17.2.0 1 / 4
17.1.0 1 / 4
17.0.1 1 / 4
17.0.0 1 / 4
16.3.1 5 / 3
16.3.0 5 / 3
16.2.1 5 / 3
16.2.0 5 / 3
16.1.12 5 / 2
5.55.0 7 / 2

v17.2.0

1 finding
LOW No provenance attestation provenance

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

v17.1.0

1 finding
LOW No provenance attestation provenance

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

v17.0.1

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.

v17.0.0

1 finding
LOW No provenance attestation provenance

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

v16.3.1

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.

v16.3.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.

v16.2.1

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.

v16.2.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.

v16.1.12

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.

v5.55.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: uikit-team → semrushinc (on 2026-05-13, known maintainer) provenance

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.