← Home

@asphalt-react/data-viz

data-viz is a comprehensive charting library tailored to fulfill diverse visualization requirements.

19
Versions
UNLICENSED
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

sayantan1211dawn29soorajjantoniomontanagoto.abhinavelayudhanira-gojekyessyprmtsr

Keywords

asphaltdata-vizdata-visualizationcomponentdlsdesign language system

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
license uncommon-license:UNLICENSED AI (license): Proprietary Gojek DLS package; UNLICENSED is intentional and consistent across the @asphalt-react namespace. ai
phantom-deps phantom-dep:@visx/vendor AI (phantom-deps): @visx/vendor is explicitly declared as a runtime dependency; phantom-dep heuristic is a false positive here. ai

Versions (showing 19 of 19)

Version Deps Published
2.15.2 16 / 2
2.15.1 16 / 2
2.15.0 16 / 2
2.14.0 16 / 2
2.12.2 17 / 2
2.12.0 17 / 2
2.11.0 17 / 2
2.10.0 17 / 2
2.9.0 17 / 2
2.8.1 17 / 2
2.8.0 17 / 2
2.7.0 17 / 2
2.6.0 16 / 2
2.5.0 16 / 2
2.3.0 16 / 2
2.2.0 16 / 2
2.1.0 16 / 2
2.0.1 16 / 2
2.0.0 16 / 2

v2.3.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: goto.abhinav → elayudhanira-gojek (on 2025-04-11, known maintainer) provenance

This version was published by a different npm account (elayudhanira-gojek) than the most recent previously approved version (goto.abhinav) on 2025-04-11, but elayudhanira-gojek 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.

v2.2.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: yessyprmtsr → goto.abhinav (on 2025-03-28, known maintainer) provenance

This version was published by a different npm account (goto.abhinav) than the most recent previously approved version (yessyprmtsr) on 2025-03-28, but goto.abhinav 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.

v2.1.0

1 finding
LOW No provenance attestation provenance

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

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

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