@vtx/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 |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() used for numeric opacity coercion (eval(cg.opacity)*100); not arbitrary code execution. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped GIS map package; edit-distance match to hapi is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped GIS map package; edit-distance match to yup is coincidental. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is in a commented-out line; not executed at runtime. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 1.2.40 | 2 / 36 | |
| 1.2.39 | 2 / 36 | |
| 1.2.38 | 2 / 36 | |
| 1.2.37 | 2 / 36 | |
| 1.2.36 | 2 / 36 | |
| 1.2.35 | 2 / 36 | |
| 1.2.34 | 2 / 34 | |
| 1.2.33 | 2 / 34 | |
| 1.2.32 | 2 / 34 | |
| 1.2.31 | 2 / 34 | |
| 1.2.30 | 2 / 34 | |
| 1.2.29 | 2 / 34 | |
| 1.2.28 | 2 / 34 | |
| 1.2.27 | 2 / 34 | |
| 1.2.26 | 2 / 34 | |
| 1.2.25 | 2 / 34 | |
| 1.2.24 | 2 / 34 | |
| 1.2.23 | 2 / 34 | |
| 1.2.22 | 2 / 34 | |
| 1.2.21 | 2 / 34 | |
| 1.2.20 | 2 / 34 | |
| 1.2.19 | 2 / 34 | |
| 1.2.18 | 2 / 34 | |
| 1.2.17 | 2 / 34 | |
| 1.2.16 | 2 / 34 | |
| 1.2.15 | 2 / 34 | |
| 1.2.14 | 2 / 34 | |
| 1.2.13 | 2 / 34 | |
| 1.2.12 | 2 / 34 | |
| 1.2.11 | 2 / 34 | |
| 1.2.10 | 2 / 34 | |
| 1.2.9 | 2 / 34 | |
| 1.2.8 | 2 / 34 | |
| 1.2.7 | 2 / 34 | |
| 1.2.6 | 2 / 34 | |
| 1.2.5 | 2 / 34 | |
| 1.2.4 | 2 / 34 | |
| 1.2.3 | 2 / 34 | |
| 1.2.2 | 2 / 34 | |
| 1.2.1 | 2 / 34 | |
| 1.1.54 | 2 / 34 | |
| 1.1.53 | 2 / 34 | |
| 1.1.52 | 2 / 34 |
v1.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.