@opengeoweb/store Apache-2.0 16 versions

@opengeoweb/store

npm Repository Homepage

GeoWeb Store library for the opengeoweb project

16

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.

Source	Rule	Reason	Accepted by	When
source-diff	source-size-dropped	AI (source-diff): Package ships only dist/ with no raw source; size drop is structural, not a stub replacement.	ai	2026/06/12
phantom-deps	phantom-dep:@opengeoweb/time-slider	AI (phantom-deps): Same-org package; stable false positive.	ai	2026/06/12
phantom-deps	phantom-dep:@opengeoweb/webmap-react	AI (phantom-deps): Same-org package; stable false positive.	ai	2026/06/12
phantom-deps	phantom-dep:ol	AI (phantom-deps): Config-referenced peer dep in a geo library; stable false positive.	ai	2026/06/12
phantom-deps	phantom-dep:immer	AI (phantom-deps): Config-referenced dep; stable false positive for this package.	ai	2026/06/12
phantom-deps	phantom-dep:lodash	AI (phantom-deps): Config-referenced dep; stable false positive for this package.	ai	2026/06/12
phantom-deps	phantom-dep:@turf/turf	AI (phantom-deps): Config-referenced dep; stable false positive for this package.	ai	2026/06/12
phantom-deps	phantom-dep:react-redux	AI (phantom-deps): Config-referenced dep; stable false positive for this package.	ai	2026/06/12
phantom-deps	phantom-dep:react-router	AI (phantom-deps): Config-referenced dep; stable false positive for this package.	ai	2026/06/12
phantom-deps	phantom-dep:@reduxjs/toolkit	AI (phantom-deps): Config-referenced dep; stable false positive for this package.	ai	2026/06/12
phantom-deps	phantom-dep:@opengeoweb/shared	AI (phantom-deps): Same-org package; stable false positive.	ai	2026/06/12
phantom-deps	phantom-dep:@opengeoweb/webmap	AI (phantom-deps): Same-org package; stable false positive.	ai	2026/06/12
phantom-deps	phantom-dep:@opengeoweb/metronome	AI (phantom-deps): Same-org package; stable false positive.	ai	2026/06/12
bogus-package	bogus-package	AI (bogus-package): Established monorepo package with 120 versions; sparse README/keywords are a style choice, not spam.	ai	2026/05/15
phantom-deps	phantom-dep:@types/geojson	AI (phantom-deps): @types/geojson is a type-only dependency; not directly imported at runtime by convention.	ai	2026/05/15

Versions (showing 16 of 16)

Version	Deps	Published
19.0.0	13 / 0	2026-06-11
18.0.0	13 / 0	2026-05-28
17.3.0	13 / 0	2026-05-13
17.1.0	13 / 0	2026-04-16
17.0.1	13 / 0	2026-04-08
17.0.0	13 / 0	2026-04-01
15.3.0	13 / 0	2026-03-05
15.2.0	13 / 0	2026-02-19
15.0.0	13 / 0	2026-01-22
14.5.2	13 / 0	2026-01-13
14.5.1	13 / 0	2026-01-09
14.5.0	13 / 0	2026-01-08
14.4.0	13 / 0	2025-12-11
14.3.0	13 / 0	2025-11-27
14.2.2	13 / 0	2025-11-20
14.2.1	13 / 0	2025-11-13

v19.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: mizzi_knmi → henrikj_ (on 2026-06-11, known maintainer) provenance

This version was published by a different npm account (henrikj_) than the most recent previously approved version (mizzi_knmi) on 2026-06-11, but henrikj_ 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.

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: mizzi_knmi → 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 (mizzi_knmi) 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

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.

v17.1.0

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.

v17.0.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.

v17.0.0

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.

v15.3.0

2 findings

HIGH Publisher changed: mizzi_knmi → 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: ernstdevreede → 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.0.0

2 findings

HIGH Publisher changed: ernstdevreede → 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

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.

v14.5.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.

v14.5.0

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.

v14.4.0

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.

v14.3.0

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.

v14.2.2

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.

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.