← Home

@opengeoweb/theme

GeoWeb Theme library for the opengeoweb project

15
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

maartenpliegerernstdevreedeloescornelisknmimizzi_knmioyvindimonetriumesaliehenrikj_karoliinahautalahaavardsokarricgilapanensampo

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:i18next AI (phantom-deps): Declared dependency; referenced in config files for theme library. ai
phantom-deps phantom-dep:@mui/system AI (phantom-deps): Declared dependency; referenced in config files for theme library. ai
phantom-deps phantom-dep:@mui/material AI (phantom-deps): Declared dependency; referenced in config files for theme library. ai
phantom-deps phantom-dep:react-i18next AI (phantom-deps): Declared dependency; referenced in config files for theme library. ai
phantom-deps phantom-dep:@mui/x-date-pickers AI (phantom-deps): Declared dependency; referenced in config files for theme library. ai

Versions (showing 15 of 15)

Version Deps Published
19.3.0 5 / 1
19.2.0 5 / 1
19.1.1 5 / 1
19.1.0 5 / 1
19.0.0 5 / 1
18.0.0 5 / 1
17.2.0 5 / 1
17.1.0 5 / 1
17.0.1 5 / 1
17.0.0 5 / 1
15.1.0 5 / 1
14.4.0 5 / 1
14.3.0 5 / 1
14.2.2 5 / 1
14.2.1 6 / 1

v19.3.0

1 finding
LOW No provenance attestation provenance

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

v19.2.0

1 finding
LOW No provenance attestation provenance

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

v19.1.1

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: loescornelisknmi → onetrium (on 2026-07-06, known maintainer) provenance

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