@hpcc-js/util
hpcc-js - Utilities
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package from hpcc-systems org; name similarity to uuid is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:@xmldom/xmldom | AI (phantom-deps): @xmldom/xmldom is a declared runtime dependency; phantom-dep heuristic misfires on indirect/config usage. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 3.6.2 | 1 / 3 | |
| 3.6.1 | 1 / 3 | |
| 3.6.0 | 1 / 3 | |
| 3.5.9 | 1 / 3 | |
| 3.5.8 | 1 / 3 | |
| 3.5.7 | 1 / 3 | |
| 3.5.6 | 1 / 3 | |
| 3.5.5 | 1 / 3 | |
| 3.5.4 | 1 / 3 | |
| 3.5.2 | 1 / 3 | |
| 3.5.1 | 1 / 2 | |
| 3.5.0 | 1 / 2 | |
| 3.4.8 | 1 / 2 | |
| 3.4.6 | 1 / 1 | |
| 3.4.5 | 1 / 1 | |
| 3.4.4 | 1 / 1 | |
| 3.4.3 | 1 / 1 | |
| 3.4.2 | 1 / 1 | |
| 3.4.1 | 1 / 1 | |
| 3.4.0 | 1 / 1 | |
| 3.3.12 | 1 / 1 | |
| 3.3.11 | 1 / 1 | |
| 3.3.10 | 1 / 1 | |
| 3.3.9 | 1 / 1 | |
| 3.3.8 | 1 / 1 | |
| 3.3.7 | 1 / 1 | |
| 3.3.6 | 1 / 1 | |
| 3.3.5 | 1 / 1 | |
| 3.3.4 | 1 / 1 | |
| 3.3.3 | 1 / 1 | |
| 3.3.2 | 1 / 1 | |
| 2.53.3 | 1 / 1 | |
| 2.53.2 | 1 / 1 |
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.53.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.53.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.