@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, 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@hpcc-js/leaflet-shim | AI (dependencies): First-party sibling package within the same hpcc-js monorepo. | ai | |
| 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 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 3.6.7 | 6 / 19 | |
| 3.6.6 | 6 / 19 | |
| 3.6.5 | 6 / 19 | |
| 3.6.4 | 6 / 19 | |
| 3.6.3 | 6 / 19 | |
| 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.5.4 | 6 / 18 | |
| 3.5.2 | 6 / 18 | |
| 3.5.1 | 6 / 18 | |
| 3.5.0 | 6 / 18 | |
| 3.4.11 | 6 / 18 | |
| 3.4.10 | 6 / 18 | |
| 3.4.8 | 6 / 18 | |
| 3.4.7 | 6 / 18 | |
| 3.4.6 | 6 / 18 | |
| 3.4.5 | 6 / 18 | |
| 3.4.4 | 6 / 18 | |
| 3.4.3 | 6 / 18 | |
| 3.4.2 | 6 / 18 | |
| 3.2.7 | 6 / 18 | |
| 3.2.6 | 6 / 18 | |
| 3.2.5 | 6 / 18 | |
| 3.2.4 | 6 / 18 | |
| 3.2.3 | 6 / 18 | |
| 3.2.2 | 6 / 18 | |
| 3.2.1 | 6 / 18 | |
| 3.2.0 | 6 / 18 | |
| 3.1.1 | 6 / 18 | |
| 3.1.0 | 6 / 18 | |
| 2.79.7 | 7 / 12 | |
| 2.79.6 | 7 / 12 | |
| 2.79.5 | 7 / 12 | |
| 2.79.4 | 7 / 12 | |
| 2.79.3 | 7 / 12 |
v3.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.10
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.7
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.79.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.