@opengis/gis
<!--  -->
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:got | AI (typosquat): Scoped GIS package @opengis/gis; not a typosquat of 'got'. Edit-distance match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped GIS package @opengis/gis; not a typosquat of 'qs'. Edit-distance match is coincidental. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decodes a shapefile zip buffer for GIS export; no obfuscation or exfiltration pattern. | ai |
Versions (showing 51 of 156)
| Version | Deps | Published |
|---|---|---|
| 0.2.166 | 4 / 19 | |
| 0.2.165 | 4 / 19 | |
| 0.2.164 | 4 / 19 | |
| 0.2.163 | 2 / 19 | |
| 0.2.161 | 2 / 19 | |
| 0.2.160 | 2 / 19 | |
| 0.2.159 | 2 / 19 | |
| 0.2.158 | 2 / 19 | |
| 0.2.157 | 2 / 19 | |
| 0.2.156 | 2 / 19 | |
| 0.2.155 | 2 / 19 | |
| 0.2.154 | 2 / 19 | |
| 0.2.153 | 2 / 19 | |
| 0.2.151 | 2 / 19 | |
| 0.2.150 | 2 / 19 | |
| 0.2.149 | 2 / 19 | |
| 0.2.148 | 2 / 19 | |
| 0.2.147 | 2 / 19 | |
| 0.2.146 | 2 / 19 | |
| 0.2.145 | 2 / 19 | |
| 0.2.144 | 2 / 19 | |
| 0.2.143 | 2 / 19 | |
| 0.2.142 | 2 / 19 | |
| 0.2.141 | 2 / 19 | |
| 0.2.140 | 2 / 19 | |
| 0.2.139 | 2 / 19 | |
| 0.2.138 | 2 / 19 | |
| 0.2.137 | 2 / 19 | |
| 0.2.135 | 2 / 19 | |
| 0.2.134 | 2 / 19 | |
| 0.2.133 | 2 / 19 | |
| 0.2.132 | 2 / 19 | |
| 0.2.131 | 2 / 19 | |
| 0.2.130 | 2 / 19 | |
| 0.2.129 | 2 / 19 | |
| 0.2.128 | 2 / 19 | |
| 0.2.127 | 2 / 19 | |
| 0.2.126 | 2 / 19 | |
| 0.2.125 | 2 / 19 | |
| 0.2.124 | 2 / 19 | |
| 0.2.123 | 2 / 19 | |
| 0.2.122 | 2 / 19 | |
| 0.2.121 | 2 / 19 | |
| 0.2.120 | 2 / 19 | |
| 0.2.119 | 2 / 19 | |
| 0.2.118 | 2 / 19 | |
| 0.2.117 | 2 / 19 | |
| 0.2.116 | 2 / 20 | |
| 0.2.115 | 2 / 20 | |
| 0.2.114 | 2 / 20 | |
| 0.2.113 | 2 / 20 |
v0.2.166
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.165
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.164
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (serebasikk) than the most recent previously approved version (artem_maniakin) on 2026-07-23, but serebasikk is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.163
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (setebosu) than the most recent previously approved version (artem_maniakin) on 2026-07-22, but setebosu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.161
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (artem_maniakin) than the most recent previously approved version (mchernenko) on 2026-07-17, but artem_maniakin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.160
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mchernenko) than the most recent previously approved version (aponasko) on 2026-07-08, but mchernenko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.159
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aponasko) than the most recent previously approved version (mchernenko) on 2026-07-03, but aponasko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.158
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mchernenko) than the most recent previously approved version (aponasko) on 2026-07-01, but mchernenko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.157
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mchernenko) than the most recent previously approved version (aponasko) on 2026-06-29, but mchernenko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.156
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aponasko) than the most recent previously approved version (mchernenko) on 2026-06-29, but aponasko is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.