@hpcc-js/api
hpcc-js - Viz api
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:hapi | AI (typosquat): Scoped @hpcc-js package in long-established monorepo; string proximity to 'hapi' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same monorepo context; no impersonation of 'pg'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same monorepo context; no impersonation of 'joi'. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Same monorepo context; no impersonation of 'ajv'. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 3.5.6 | 1 / 5 | |
| 3.5.5 | 1 / 5 | |
| 3.5.4 | 1 / 5 | |
| 3.5.3 | 1 / 5 | |
| 3.5.2 | 1 / 5 | |
| 3.5.1 | 1 / 5 | |
| 3.5.0 | 1 / 5 | |
| 3.4.20 | 1 / 5 | |
| 3.4.19 | 1 / 5 | |
| 3.4.18 | 1 / 5 | |
| 3.4.17 | 1 / 5 | |
| 3.4.16 | 1 / 5 | |
| 3.4.15 | 1 / 5 | |
| 3.4.13 | 1 / 5 | |
| 3.4.12 | 1 / 5 | |
| 3.4.11 | 1 / 5 | |
| 3.4.10 | 1 / 5 | |
| 3.4.9 | 1 / 5 | |
| 3.4.7 | 1 / 5 | |
| 3.4.6 | 1 / 5 | |
| 3.4.5 | 1 / 5 | |
| 3.4.4 | 1 / 5 | |
| 3.4.3 | 1 / 5 | |
| 3.4.2 | 1 / 5 | |
| 3.4.1 | 1 / 5 | |
| 3.4.0 | 1 / 5 | |
| 3.3.12 | 1 / 5 | |
| 3.3.11 | 1 / 5 | |
| 3.3.10 | 1 / 5 | |
| 3.3.9 | 1 / 5 | |
| 3.3.8 | 1 / 5 | |
| 3.3.7 | 1 / 5 | |
| 3.3.6 | 1 / 5 | |
| 3.3.5 | 1 / 5 | |
| 3.3.4 | 1 / 5 | |
| 3.3.3 | 1 / 5 | |
| 3.3.2 | 1 / 5 | |
| 3.3.1 | 1 / 5 | |
| 3.3.0 | 1 / 5 | |
| 3.2.0 | 1 / 5 | |
| 3.1.0 | 1 / 5 | |
| 2.14.6 | 1 / 6 | |
| 2.14.5 | 1 / 6 | |
| 2.14.4 | 1 / 6 | |
| 2.14.3 | 1 / 6 |
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.