@hpcc-js/chart
hpcc-js - Viz Chart
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:chalk | AI (typosquat): Scoped @hpcc-js/chart is a legitimate visualization package, not a typosquat of chalk; Levenshtein match is coincidental. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 3.8.6 | 3 / 22 | |
| 3.8.5 | 3 / 22 | |
| 3.8.4 | 3 / 22 | |
| 3.8.3 | 3 / 22 | |
| 3.8.2 | 3 / 22 | |
| 3.8.1 | 3 / 22 | |
| 3.8.0 | 3 / 22 | |
| 3.7.9 | 3 / 22 | |
| 3.7.8 | 3 / 22 | |
| 3.7.7 | 3 / 22 | |
| 3.7.6 | 3 / 22 | |
| 3.7.5 | 3 / 22 | |
| 3.7.4 | 3 / 22 | |
| 3.7.2 | 3 / 22 | |
| 3.7.1 | 3 / 22 | |
| 3.7.0 | 3 / 22 | |
| 3.6.6 | 3 / 22 | |
| 3.6.5 | 3 / 22 | |
| 3.6.3 | 3 / 22 | |
| 3.6.2 | 3 / 22 | |
| 3.6.1 | 3 / 22 | |
| 3.6.0 | 3 / 22 | |
| 3.5.3 | 3 / 22 | |
| 3.5.2 | 3 / 22 | |
| 3.5.1 | 3 / 22 | |
| 3.5.0 | 3 / 22 | |
| 3.4.3 | 3 / 22 | |
| 3.4.2 | 3 / 22 | |
| 3.4.1 | 3 / 22 | |
| 3.4.0 | 3 / 22 | |
| 3.3.9 | 3 / 22 | |
| 3.3.8 | 3 / 22 | |
| 3.3.7 | 3 / 22 | |
| 3.3.6 | 3 / 22 | |
| 3.3.5 | 3 / 22 | |
| 3.3.4 | 3 / 22 | |
| 3.3.3 | 3 / 22 | |
| 3.3.2 | 3 / 22 | |
| 3.3.1 | 3 / 22 | |
| 3.3.0 | 3 / 22 | |
| 3.2.0 | 3 / 22 | |
| 2.86.6 | 3 / 24 | |
| 2.86.5 | 3 / 24 | |
| 2.86.4 | 3 / 24 | |
| 2.86.3 | 3 / 24 |
v3.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.