@opengeoweb/layer-select

GeoWeb layer select library for the opengeoweb project

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
provenance	no-provenance	AI (provenance): No provenance has been a consistent pattern for this package; not a new risk signal.	ai	2026/05/30
provenance	publisher-changed	AI (provenance): New publisher has 62 approved packages; consistent with org maintainer rotation for this established package.	ai	2026/05/30
bogus-package	bogus-package	AI (bogus-package): Established monorepo package with 104 versions; sparse README/keywords is a style choice, not spam.	ai	2026/05/18
phantom-deps	phantom-dep:react-window	AI (phantom-deps): Pre-bundled ESM; deps declared for consumers but not directly imported in dist output.	ai	2026/05/15
phantom-deps	phantom-dep:@mui/material	AI (phantom-deps): Pre-bundled ESM; deps declared for consumers but not directly imported in dist output.	ai	2026/05/15
phantom-deps	phantom-dep:react-i18next	AI (phantom-deps): Pre-bundled ESM; deps declared for consumers but not directly imported in dist output.	ai	2026/05/15
phantom-deps	phantom-dep:react-hook-form	AI (phantom-deps): Pre-bundled ESM; deps declared for consumers but not directly imported in dist output.	ai	2026/05/15
phantom-deps	phantom-dep:@reduxjs/toolkit	AI (phantom-deps): Pre-bundled ESM; deps declared for consumers but not directly imported in dist output.	ai	2026/05/15
phantom-deps	phantom-dep:@opengeoweb/store	AI (phantom-deps): Same-org sibling; monorepo pattern.	ai	2026/05/15
phantom-deps	phantom-dep:lodash	AI (phantom-deps): Pre-bundled ESM; deps declared for consumers but not directly imported in dist output.	ai	2026/05/15
phantom-deps	phantom-dep:@opengeoweb/shared	AI (phantom-deps): Same-org sibling; monorepo pattern.	ai	2026/05/15
phantom-deps	phantom-dep:@opengeoweb/webmap	AI (phantom-deps): Same-org sibling; monorepo pattern.	ai	2026/05/15
phantom-deps	phantom-dep:@opengeoweb/snackbar	AI (phantom-deps): Same-org sibling; monorepo pattern.	ai	2026/05/15
phantom-deps	phantom-dep:@opengeoweb/form-fields	AI (phantom-deps): Same-org sibling; monorepo pattern.	ai	2026/05/15
phantom-deps	phantom-dep:@opengeoweb/webmap-react	AI (phantom-deps): Same-org sibling; monorepo pattern.	ai	2026/05/15
phantom-deps	phantom-dep:@opengeoweb/theme	AI (phantom-deps): Same-org sibling; monorepo pattern.	ai	2026/05/15
phantom-deps	phantom-dep:i18next	AI (phantom-deps): Pre-bundled ESM; deps declared for consumers but not directly imported in dist output.	ai	2026/05/15
phantom-deps	phantom-dep:react-redux	AI (phantom-deps): Pre-bundled ESM; deps declared for consumers but not directly imported in dist output.	ai	2026/05/15

Versions (showing 18 of 18)

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

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

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

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: mizzi_knmi → 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: mizzi_knmi → 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: mizzi_knmi → 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: mizzi_knmi → 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.