@hpcc-js/map
hpcc-js - Viz Map
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.es6.js | AI (source-diff): Standard rollup bundle output; long lines are minified JS, not obfuscation. Stable pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @hpcc-js package from hpcc-systems org; not a typosquat of hapi. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @hpcc-js package from hpcc-systems org; not a typosquat of yup. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.6.2 | 6 / 18 | |
| 3.6.1 | 6 / 18 | |
| 3.6.0 | 6 / 18 | |
| 3.5.9 | 6 / 18 | |
| 3.5.8 | 6 / 18 | |
| 3.5.7 | 6 / 18 | |
| 3.5.6 | 6 / 18 | |
| 3.5.5 | 6 / 18 | |
| 3.2.7 | 6 / 18 | |
| 3.2.6 | 6 / 18 | |
| 2.79.7 | 7 / 12 |
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. 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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.