@hpcc-js/eclwatch
hpcc-js - ECL Watch
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of Sigstore provenance is consistent across all versions. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 3.8.5 | 10 / 2 | |
| 3.8.4 | 10 / 2 | |
| 3.8.3 | 10 / 2 | |
| 3.8.2 | 10 / 2 | |
| 3.8.1 | 10 / 2 | |
| 3.8.0 | 10 / 2 | |
| 3.7.2 | 10 / 2 | |
| 3.7.1 | 10 / 2 | |
| 3.7.0 | 10 / 2 | |
| 3.6.13 | 10 / 2 | |
| 3.6.12 | 10 / 2 | |
| 3.6.11 | 10 / 2 | |
| 3.6.10 | 10 / 2 | |
| 3.6.9 | 10 / 2 | |
| 3.6.8 | 10 / 2 | |
| 3.6.7 | 10 / 2 | |
| 3.6.6 | 10 / 2 | |
| 3.6.5 | 10 / 2 | |
| 3.6.3 | 10 / 2 | |
| 3.6.2 | 10 / 2 | |
| 3.6.1 | 10 / 2 | |
| 3.6.0 | 10 / 2 | |
| 3.5.11 | 10 / 2 | |
| 3.5.10 | 10 / 2 | |
| 3.5.8 | 10 / 2 | |
| 3.5.7 | 10 / 2 | |
| 3.5.6 | 10 / 2 | |
| 3.5.5 | 10 / 2 | |
| 3.5.4 | 10 / 2 | |
| 3.5.3 | 10 / 2 | |
| 3.5.2 | 10 / 2 | |
| 3.5.1 | 10 / 2 | |
| 3.5.0 | 10 / 2 | |
| 3.4.1 | 10 / 2 | |
| 3.4.0 | 10 / 2 | |
| 3.3.6 | 10 / 2 | |
| 3.3.5 | 10 / 2 | |
| 3.3.4 | 10 / 2 | |
| 3.3.3 | 10 / 2 | |
| 3.3.2 | 10 / 2 | |
| 3.3.1 | 10 / 2 | |
| 3.3.0 | 10 / 2 | |
| 3.2.20 | 10 / 2 | |
| 3.2.19 | 10 / 2 | |
| 3.2.18 | 10 / 2 | |
| 3.2.17 | 10 / 2 | |
| 3.2.16 | 10 / 2 | |
| 3.2.15 | 10 / 2 | |
| 3.2.14 | 10 / 2 | |
| 3.2.13 | 10 / 2 | |
| 3.2.12 | 10 / 2 | |
| 3.2.11 | 10 / 2 | |
| 3.2.10 | 10 / 2 | |
| 3.2.9 | 10 / 2 | |
| 3.2.8 | 10 / 2 | |
| 3.2.7 | 10 / 2 | |
| 3.2.6 | 10 / 2 | |
| 3.2.5 | 10 / 2 | |
| 3.2.4 | 10 / 2 | |
| 3.2.3 | 10 / 2 | |
| 3.2.2 | 10 / 2 | |
| 3.2.1 | 10 / 2 | |
| 3.2.0 | 10 / 2 | |
| 3.1.1 | 10 / 2 | |
| 3.1.0 | 10 / 2 | |
| 2.77.11 | 10 / 3 | |
| 2.77.10 | 10 / 3 | |
| 2.77.9 | 10 / 3 | |
| 2.77.8 | 10 / 3 | |
| 2.77.7 | 10 / 3 |
v3.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
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.2.6
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.2.5
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.2.4
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.2.3
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.2.2
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.2.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.2.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.
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.