← Home

@semcore/data-table

npm Repository Homepage

Semrush DataTable 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
phantom-deps phantom-dep:@semcore/flex-box AI (phantom-deps): Same-org @semcore scope; phantom-dep heuristic unreliable for monorepo packages. ai
phantom-deps phantom-dep:@semcore/scroll-area AI (phantom-deps): Same-org @semcore scope; phantom-dep heuristic unreliable for monorepo packages. ai
dependencies unvetted-dep:@semcore/spin AI (dependencies): Sibling @semcore monorepo package from same Semrush org; stable false positive for this package family. ai
dependencies unvetted-dep:@semcore/button AI (dependencies): Sibling @semcore monorepo package from same Semrush org; stable false positive for this package family. ai
dependencies unvetted-dep:@semcore/widget-empty AI (dependencies): Sibling @semcore monorepo package from same Semrush org; stable false positive for this package family. ai

Versions (showing 9 of 9)

Version Deps Published
17.2.0 5 / 15
17.1.0 5 / 15
17.0.2 5 / 15
16.7.1 8 / 15
16.7.0 8 / 15
16.6.0 8 / 15
16.5.2 8 / 15
16.5.0 8 / 15
16.4.4 8 / 15

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

1 finding
LOW No provenance attestation provenance

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

v16.7.0

1 finding
LOW No provenance attestation provenance

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

v16.6.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.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.5.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.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.