@semcore/d3-chart MIT 13 versions

@semcore/d3-chart

npm Repository Homepage

Semrush D3 Chart Component

13

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.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@semcore/utils	AI (dependencies): @semcore/utils is a first-party sibling package from the same Semrush UI kit monorepo; not a third-party risk.	ai	2026/05/29
phantom-deps	phantom-dep:d3-time	AI (phantom-deps): Transitive dependency via d3-scale; stable pattern for D3 packages.	ai	2026/05/27
phantom-deps	phantom-dep:d3-time-format	AI (phantom-deps): Transitive dependency via d3-scale; stable pattern for D3 packages.	ai	2026/05/27
phantom-deps	phantom-dep:@types/d3-shape	AI (phantom-deps): Type definitions for d3-shape dependency; convention-loaded by TypeScript.	ai	2026/05/27

Versions (showing 13 of 13)

Version	Deps	Published
17.2.0	15 / 14	2026-06-05
17.1.0	15 / 14	2026-05-14
17.0.2	15 / 14	2026-04-30
17.0.1	15 / 14	2026-04-16
17.0.0	15 / 14	2026-04-15
16.7.1	19 / 14	2026-05-13
16.7.0	19 / 14	2026-05-13
16.6.0	19 / 14	2026-04-02
16.5.0	19 / 14	2026-02-10
16.4.2	19 / 14	2025-12-18
16.4.1	19 / 14	2025-12-01
16.4.0	19 / 14	2025-11-18
3.61.0	20 / 14	2026-05-13

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

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.7.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.7.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.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.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.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.4.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.4.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.61.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.