@hpcc-js/form
hpcc-js - Viz Form
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:cors | AI (typosquat): Scoped @hpcc-js org package; Levenshtein match to 'cors' is coincidental, no impersonation intent. | ai | |
| phantom-deps | phantom-dep:@hpcc-js/chart | AI (phantom-deps): Same-org sibling dep; phantom detection is a known false positive for monorepo packages. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 3.5.6 | 3 / 6 | |
| 3.5.5 | 3 / 6 | |
| 3.5.4 | 3 / 6 | |
| 3.5.3 | 3 / 6 | |
| 3.5.2 | 3 / 6 | |
| 3.5.1 | 3 / 6 | |
| 3.5.0 | 3 / 6 | |
| 3.4.9 | 3 / 6 | |
| 3.4.8 | 3 / 6 | |
| 3.4.7 | 3 / 6 | |
| 3.4.6 | 3 / 6 | |
| 3.4.5 | 3 / 6 | |
| 3.4.4 | 3 / 6 | |
| 3.4.2 | 3 / 6 | |
| 3.4.1 | 3 / 6 | |
| 3.4.0 | 3 / 6 | |
| 3.3.10 | 3 / 6 | |
| 3.3.9 | 3 / 6 | |
| 3.3.7 | 3 / 6 | |
| 3.3.6 | 3 / 6 | |
| 3.3.5 | 3 / 6 | |
| 3.3.4 | 3 / 6 | |
| 3.3.3 | 3 / 6 | |
| 3.3.2 | 3 / 6 | |
| 3.3.1 | 3 / 6 | |
| 3.3.0 | 3 / 6 | |
| 3.2.13 | 3 / 6 | |
| 3.2.12 | 3 / 6 | |
| 3.2.11 | 3 / 6 | |
| 3.2.10 | 3 / 6 | |
| 3.2.9 | 3 / 6 | |
| 3.2.8 | 3 / 6 | |
| 3.2.7 | 3 / 6 | |
| 3.2.6 | 3 / 6 | |
| 3.2.5 | 3 / 6 | |
| 3.2.4 | 3 / 6 | |
| 3.2.3 | 3 / 6 | |
| 3.2.2 | 3 / 6 | |
| 3.2.1 | 3 / 6 | |
| 3.2.0 | 3 / 6 | |
| 3.1.0 | 3 / 6 | |
| 2.12.7 | 3 / 7 | |
| 2.12.6 | 3 / 7 | |
| 2.12.5 | 3 / 7 | |
| 2.12.4 | 3 / 7 | |
| 2.12.3 | 3 / 7 |
v3.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
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.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.