← Home

@opengeoweb/api

npm Repository Homepage

GeoWeb API library for the opengeoweb project

18
Versions
Apache-2.0
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

maartenpliegerernstdevreedeloescornelisknmimizzi_knmioyvindimonetriumesaliehenrikj_karoliinahautalahaavardsokarricgilapanensampo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): maartenplieger is an established publisher in the same org with strong approval history; transition appears legitimate. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package; distance-2 match to 'pg' is not meaningful for @opengeoweb/api. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package; distance-2 match to 'joi' is not meaningful for @opengeoweb/api. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped package; distance-2 match to 'ajv' is not meaningful for @opengeoweb/api. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): Likely used in build/config tooling; stable false positive for this package. ai
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped package @opengeoweb/api; Levenshtein match to 'hapi' is a false positive for this org-scoped name. ai
phantom-deps phantom-dep:@opengeoweb/authentication AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for monorepo packages. ai
phantom-deps phantom-dep:@tanstack/query-core AI (phantom-deps): Referenced in config files; stable false positive for this build-output package. ai
phantom-deps phantom-dep:@tanstack/react-query AI (phantom-deps): Referenced in config files; stable false positive for this build-output package. ai
phantom-deps phantom-dep:@tanstack/react-query-devtools AI (phantom-deps): Referenced in config files; stable false positive for this build-output package. ai
phantom-deps phantom-dep:@opengeoweb/store AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic unreliable for monorepo packages. ai

Versions (showing 18 of 18)

Version Deps Published
18.0.0 6 / 0
17.3.0 6 / 0
17.2.0 6 / 0
17.1.0 6 / 0
17.0.1 7 / 0
17.0.0 7 / 0
16.0.0 7 / 0
15.3.0 7 / 0
15.2.0 7 / 0
15.1.0 7 / 0
15.0.0 7 / 0
14.5.2 7 / 0
14.5.1 7 / 0
14.5.0 7 / 0
14.4.0 7 / 0
14.3.0 7 / 0
14.2.2 7 / 0
14.2.1 7 / 0

v18.0.0

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: maartenplieger → oyvindim (on 2026-05-28, known maintainer) provenance

This version was published by a different npm account (oyvindim) than the most recent previously approved version (maartenplieger) on 2026-05-28, but oyvindim 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.

v17.3.0

2 findings
HIGH Publisher changed: karoliinahautala → maartenplieger (on 2026-05-13) provenance

This version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v17.2.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@opengeoweb/api' is 1 edit(s) away from popular package 'hapi'.

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.

v17.1.0

2 findings
HIGH Publisher changed: henrikj_ → karricgi (on 2026-04-16) provenance

This version was published by a different npm account than previous versions on 2026-04-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v17.0.1

2 findings
HIGH Publisher changed: henrikj_ → mizzi_knmi (on 2026-04-08) provenance

This version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v17.0.0

2 findings
HIGH Publisher changed: henrikj_ → loescornelisknmi (on 2026-04-01) provenance

This version was published by a different npm account than previous versions on 2026-04-01. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v16.0.0

2 findings
HIGH Publisher changed: henrikj_ → esalie (on 2026-03-19) provenance

This version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v15.3.0

2 findings
HIGH Publisher changed: henrikj_ → haavardso (on 2026-03-05) provenance

This version was published by a different npm account than previous versions on 2026-03-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v15.2.0

2 findings
HIGH Publisher changed: henrikj_ → loescornelisknmi (on 2026-02-19) provenance

This version was published by a different npm account than previous versions on 2026-02-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v15.1.0

2 findings
HIGH Publisher changed: henrikj_ → oyvindim (on 2026-02-05) provenance

This version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v15.0.0

2 findings
HIGH Publisher changed: henrikj_ → onetrium (on 2026-01-22) provenance

This version was published by a different npm account than previous versions on 2026-01-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v14.5.2

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@opengeoweb/api' is 1 edit(s) away from popular package 'hapi'.

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.

v14.5.1

2 findings
HIGH Publisher changed: ernstdevreede → mizzi_knmi (on 2026-01-09) provenance

This version was published by a different npm account than previous versions on 2026-01-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v14.5.0

2 findings
HIGH Publisher changed: ernstdevreede → mizzi_knmi (on 2026-01-08) provenance

This version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v14.4.0

1 finding
LOW No provenance attestation provenance

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

v14.3.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@opengeoweb/api' is 1 edit(s) away from popular package 'hapi'.

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.

v14.2.2

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@opengeoweb/api' is 1 edit(s) away from popular package 'hapi'.

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.

v14.2.1

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.