@hpcc-js/react
hpcc-js - Viz React
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.es6.js | AI (source-diff): Standard rollup bundle output; minified lines are preact/component code, not obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Long-established hpcc-js org package; lack of provenance is consistent across all their releases. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 3.5.6 | 1 / 3 | |
| 3.5.5 | 1 / 3 | |
| 3.5.4 | 1 / 3 | |
| 3.5.3 | 1 / 3 | |
| 3.5.2 | 1 / 3 | |
| 3.5.0 | 1 / 3 | |
| 3.4.20 | 1 / 3 | |
| 3.4.19 | 1 / 3 | |
| 3.4.18 | 1 / 3 | |
| 3.4.17 | 1 / 3 | |
| 3.4.16 | 1 / 3 | |
| 3.4.15 | 1 / 3 | |
| 3.4.13 | 1 / 3 | |
| 3.4.12 | 1 / 3 | |
| 3.4.11 | 1 / 3 | |
| 3.4.10 | 1 / 3 | |
| 3.4.9 | 1 / 3 | |
| 3.4.7 | 1 / 3 | |
| 3.4.6 | 1 / 3 | |
| 3.4.5 | 1 / 3 | |
| 3.4.4 | 1 / 3 | |
| 3.4.3 | 1 / 3 | |
| 3.4.2 | 1 / 3 | |
| 3.4.1 | 1 / 3 | |
| 3.4.0 | 1 / 3 | |
| 3.3.2 | 1 / 3 | |
| 3.3.1 | 1 / 3 | |
| 3.3.0 | 1 / 3 | |
| 3.2.10 | 1 / 3 | |
| 3.2.9 | 1 / 3 | |
| 3.2.8 | 1 / 3 | |
| 3.2.7 | 1 / 3 | |
| 3.2.6 | 1 / 3 | |
| 3.2.5 | 1 / 3 | |
| 3.2.4 | 1 / 3 | |
| 3.2.3 | 1 / 3 | |
| 3.2.2 | 1 / 3 | |
| 3.2.1 | 1 / 3 | |
| 3.2.0 | 1 / 3 | |
| 3.1.1 | 1 / 2 | |
| 3.1.0 | 1 / 3 | |
| 2.55.6 | 2 / 2 | |
| 2.55.5 | 2 / 2 | |
| 2.55.4 | 2 / 2 | |
| 2.55.3 | 2 / 2 |
v3.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.