← Home

@semcore/base-trigger

npm Repository Homepage

Semrush BaseTrigger Component

9
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
dependencies unvetted-dep:@semcore/utils AI (dependencies): First-party @semcore monorepo package; stable false positive for this package family. ai
dependencies unvetted-dep:@semcore/dot AI (dependencies): Sibling package from same semrush/intergalactic monorepo; consistent with the rest of the @semcore/* dependency graph. ai
dependencies unvetted-dep:@semcore/spin AI (dependencies): Sibling package from same semrush/intergalactic monorepo; consistent with the rest of the @semcore/* dependency graph. ai
phantom-deps phantom-dep:@semcore/tooltip AI (phantom-deps): @semcore/tooltip is in devDependencies; phantom-dep fires as false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
17.2.0 5 / 5
17.1.0 5 / 5
17.0.1 5 / 5
17.0.0 5 / 5
16.5.1 6 / 3
16.5.0 6 / 3
16.4.5 6 / 3
16.4.4 6 / 3
4.54.0 7 / 3

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

v16.5.1

1 finding
LOW No provenance attestation provenance

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

v16.5.0

1 finding
LOW No provenance attestation provenance

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

v16.4.5

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

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.

v4.54.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.