← Home

@semcore/ui

npm Repository Homepage

Semrush design system package that reexports all other single component packages.

16
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): @semcore/icon is a first-party dep from the same monorepo; addition is expected as the package expands its component set. ai
source-diff large-new-source-files AI (source-diff): 3516 new files are icon components from @semcore/icon bundled into the umbrella package; benign for this package. ai
source-diff source-size-tripled AI (source-diff): Size increase is entirely attributable to bundled icon assets from the newly added @semcore/icon dependency. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Same false-positive pattern for scoped package vs short unscoped name. ai
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped package @semcore/ui; Levenshtein match to short unscoped names is a systematic false positive. ai
semgrep semgrep:dynamic-require AI (semgrep): Build-time utility checking for default exports; not a runtime arbitrary-module-load risk. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Same false-positive pattern for scoped package vs short unscoped name. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Same false-positive pattern for scoped package vs short unscoped name. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Same false-positive pattern for scoped package vs short unscoped name. ai

Versions (showing 16 of 16)

Version Deps Published
17.2.0 62 / 8
17.1.2 61 / 8
17.1.1 61 / 8
17.1.0 61 / 8
17.0.2 62 / 8
17.0.1 62 / 8
17.0.0 62 / 8
16.16.1 76 / 8
16.16.0 76 / 8
16.15.0 77 / 8
16.14.0 77 / 8
16.13.2 77 / 8
16.13.1 77 / 8
16.13.0 77 / 8
16.12.0 76 / 8
15.132.0 76 / 9

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

1 finding
LOW No provenance attestation provenance

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

v17.1.1

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

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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v16.16.1

1 finding
LOW No provenance attestation provenance

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

v16.16.0

1 finding
LOW No provenance attestation provenance

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

v16.15.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.14.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.13.2

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.13.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.13.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.12.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.

v15.132.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.