← Home

@opengis/gis

npm

<!-- ![alt text](https://cdn.softpro.ua/data/npm/admin/opengis-admin.png) -->

44
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

evheniihavryliukandrii.cherinsetebosurapax.deusmchernenkoserebasikkartem_maniakinaponaskofarizov_maximbohdana_usenko

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 44 of 145)

Version Deps Published
0.2.49 2 / 20
0.2.48 2 / 20
0.2.47 2 / 20
0.2.46 2 / 20
0.2.45 2 / 20
0.2.44 2 / 20
0.2.43 2 / 20
0.2.42 2 / 20
0.2.41 2 / 20
0.2.40 2 / 20
0.2.38 2 / 20
0.2.37 2 / 20
0.2.36 2 / 20
0.2.35 2 / 20
0.2.34 2 / 20
0.2.33 2 / 20
0.2.32 2 / 20
0.2.31 2 / 20
0.2.30 2 / 20
0.2.29 2 / 20
0.2.28 2 / 20
0.2.27 2 / 20
0.2.26 2 / 20
0.2.25 2 / 20
0.2.23 2 / 20
0.2.22 2 / 20
0.2.21 2 / 20
0.2.20 2 / 20
0.2.19 2 / 20
0.2.18 2 / 20
0.2.17 2 / 20
0.2.16 2 / 20
0.2.15 2 / 20
0.2.14 2 / 20
0.2.13 2 / 20
0.2.12 2 / 20
0.2.11 2 / 20
0.2.10 2 / 20
0.2.9 2 / 20
0.2.8 2 / 20
0.2.7 2 / 20
0.1.82 2 / 17
0.1.76 2 / 14
0.1.73 2 / 12

v0.2.49

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: artem_maniakin → setebosu (on 2026-01-22, known maintainer) provenance

This version was published by a different npm account (setebosu) than the most recent previously approved version (artem_maniakin) on 2026-01-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.48

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: artem_maniakin → mchernenko (on 2026-01-21, known maintainer) provenance

This version was published by a different npm account (mchernenko) than the most recent previously approved version (artem_maniakin) on 2026-01-21, 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.47

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: artem_maniakin → mchernenko (on 2026-01-21, known maintainer) provenance

This version was published by a different npm account (mchernenko) than the most recent previously approved version (artem_maniakin) on 2026-01-21, 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.46

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: artem_maniakin → mchernenko (on 2026-01-21, known maintainer) provenance

This version was published by a different npm account (mchernenko) than the most recent previously approved version (artem_maniakin) on 2026-01-21, 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.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.44

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: artem_maniakin → aponasko (on 2026-01-16, known maintainer) provenance

This version was published by a different npm account (aponasko) than the most recent previously approved version (artem_maniakin) on 2026-01-16, 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.43

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.42

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: farizov_maxim → artem_maniakin (on 2026-01-16, known maintainer) provenance

This version was published by a different npm account (artem_maniakin) than the most recent previously approved version (farizov_maxim) on 2026-01-16, 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.41

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: farizov_maxim → artem_maniakin (on 2026-01-15, known maintainer) provenance

This version was published by a different npm account (artem_maniakin) than the most recent previously approved version (farizov_maxim) on 2026-01-15, 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.40

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.38

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.37

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: farizov_maxim → aponasko (on 2026-01-14, known maintainer) provenance

This version was published by a different npm account (aponasko) than the most recent previously approved version (farizov_maxim) on 2026-01-14, 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.36

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: farizov_maxim → aponasko (on 2026-01-14, known maintainer) provenance

This version was published by a different npm account (aponasko) than the most recent previously approved version (farizov_maxim) on 2026-01-14, 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.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.34

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mchernenko → farizov_maxim (on 2026-01-14, known maintainer) provenance

This version was published by a different npm account (farizov_maxim) than the most recent previously approved version (mchernenko) on 2026-01-14, but farizov_maxim 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.33

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: aponasko → artem_maniakin (on 2026-01-14, known maintainer) provenance

This version was published by a different npm account (artem_maniakin) than the most recent previously approved version (aponasko) on 2026-01-14, 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.32

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: aponasko → mchernenko (on 2026-01-13, known maintainer) provenance

This version was published by a different npm account (mchernenko) than the most recent previously approved version (aponasko) on 2026-01-13, 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.31

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: aponasko → mchernenko (on 2026-01-13, known maintainer) provenance

This version was published by a different npm account (mchernenko) than the most recent previously approved version (aponasko) on 2026-01-13, 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.30

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: aponasko → farizov_maxim (on 2026-01-13, known maintainer) provenance

This version was published by a different npm account (farizov_maxim) than the most recent previously approved version (aponasko) on 2026-01-13, but farizov_maxim 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.29

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: aponasko → mchernenko (on 2026-01-13, known maintainer) provenance

This version was published by a different npm account (mchernenko) than the most recent previously approved version (aponasko) on 2026-01-13, 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.28

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: aponasko → artem_maniakin (on 2026-01-13, known maintainer) provenance

This version was published by a different npm account (artem_maniakin) than the most recent previously approved version (aponasko) on 2026-01-13, 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.27

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: aponasko → mchernenko (on 2026-01-12, known maintainer) provenance

This version was published by a different npm account (mchernenko) than the most recent previously approved version (aponasko) on 2026-01-12, 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.26

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: setebosu → aponasko (on 2026-01-09, known maintainer) provenance

This version was published by a different npm account (aponasko) than the most recent previously approved version (setebosu) on 2026-01-09, 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.25

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: setebosu → farizov_maxim (on 2026-01-08, known maintainer) provenance

This version was published by a different npm account (farizov_maxim) than the most recent previously approved version (setebosu) on 2026-01-08, but farizov_maxim 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.23

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: setebosu → aponasko (on 2026-01-08, known maintainer) provenance

This version was published by a different npm account (aponasko) than the most recent previously approved version (setebosu) on 2026-01-08, 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.22

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: setebosu → farizov_maxim (on 2026-01-07, known maintainer) provenance

This version was published by a different npm account (farizov_maxim) than the most recent previously approved version (setebosu) on 2026-01-07, but farizov_maxim 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.21

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: setebosu → mchernenko (on 2026-01-06, known maintainer) provenance

This version was published by a different npm account (mchernenko) than the most recent previously approved version (setebosu) on 2026-01-06, 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.20

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: setebosu → artem_maniakin (on 2026-01-06, known maintainer) provenance

This version was published by a different npm account (artem_maniakin) than the most recent previously approved version (setebosu) on 2026-01-06, 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.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.18

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: artem_maniakin → setebosu (on 2026-01-05, known maintainer) provenance

This version was published by a different npm account (setebosu) than the most recent previously approved version (artem_maniakin) on 2026-01-05, 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.17

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: artem_maniakin → farizov_maxim (on 2025-12-30, known maintainer) provenance

This version was published by a different npm account (farizov_maxim) than the most recent previously approved version (artem_maniakin) on 2025-12-30, but farizov_maxim 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.16

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: artem_maniakin → farizov_maxim (on 2025-12-30, known maintainer) provenance

This version was published by a different npm account (farizov_maxim) than the most recent previously approved version (artem_maniakin) on 2025-12-30, but farizov_maxim 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.15

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: artem_maniakin → farizov_maxim (on 2025-12-26, known maintainer) provenance

This version was published by a different npm account (farizov_maxim) than the most recent previously approved version (artem_maniakin) on 2025-12-26, but farizov_maxim 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.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.82

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.76

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.73

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.