← Home

@opengeoweb/webmap

npm Repository Homepage
9
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

maartenpliegerernstdevreedeloescornelisknmimizzi_knmioyvindimonetriumesaliehenrikj_karoliinahautalahaavardsokarricgilapanensampo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:lodash AI (phantom-deps): Monorepo sub-package; lodash used indirectly via config/build tooling, stable pattern. ai
phantom-deps phantom-dep:i18next AI (phantom-deps): i18next referenced in config files, not directly imported; stable for this package. ai
phantom-deps phantom-dep:@types/geojson AI (phantom-deps): Type-only package loaded by convention; stable false positive for this package. ai
phantom-deps phantom-dep:@opengeoweb/shared AI (phantom-deps): Same-org sibling dep; indirect usage pattern is stable for this monorepo package. ai
phantom-deps phantom-dep:@tanstack/query-core AI (phantom-deps): Referenced in config files; stable indirect usage pattern for this package. ai
bogus-package bogus-package AI (bogus-package): Tiny payload and sparse README are consistent with a compiled monorepo sub-package; not spam. ai

Versions (showing 9 of 9)

Version Deps Published
18.0.0 5 / 0
17.2.0 5 / 0
17.0.1 5 / 0
17.0.0 5 / 0
16.0.0 5 / 0
14.4.0 5 / 0
14.3.0 5 / 0
14.2.2 5 / 0
14.2.1 5 / 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: 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.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.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.

v16.0.0

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

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

1 finding
LOW No provenance attestation provenance

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

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.