@opengeoweb/warnings
Supply chain provenance
Status for the latest visible version.
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
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): Ships prebuilt dist; src excluded from package, stable layout. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped monorepo lib; tiny payload is dist-only publish pattern. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher has strong track record (139 approved, 0 rejected); consistent org handoff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainer list change matches known publisher transition, not compromise indicator. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is a declared runtime dep; same build-output false-positive pattern. | 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:ol | AI (phantom-deps): ol is a declared runtime dep; phantom-dep heuristic fires on build output, not a real missing import. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 19.3.0 | 26 / 1 | |
| 19.2.0 | 26 / 1 | |
| 19.1.1 | 26 / 1 | |
| 19.0.0 | 26 / 1 | |
| 18.0.0 | 26 / 1 | |
| 17.0.1 | 26 / 1 | |
| 17.0.0 | 26 / 1 | |
| 16.0.0 | 26 / 1 | |
| 15.3.0 | 26 / 1 | |
| 15.2.0 | 26 / 1 | |
| 15.1.0 | 27 / 1 | |
| 15.0.0 | 27 / 1 | |
| 14.5.2 | 27 / 1 | |
| 14.5.1 | 27 / 1 | |
| 14.5.0 | 27 / 1 | |
| 14.4.0 | 27 / 1 | |
| 14.3.0 | 27 / 1 | |
| 14.2.2 | 27 / 1 | |
| 14.2.1 | 27 / 1 |
v19.3.0
2 findingsThis version was published by a different npm account than previous versions on unknown date. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mizzi_knmi) than the most recent previously approved version (haavardso) on 2026-04-08, but mizzi_knmi 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.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (loescornelisknmi) than the most recent previously approved version (esalie) on 2026-04-01, but loescornelisknmi 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.
v16.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (esalie) than the most recent previously approved version (haavardso) on 2026-03-19, but esalie 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.
v15.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (haavardso) than the most recent previously approved version (loescornelisknmi) on 2026-03-05, but haavardso 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.
v15.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (loescornelisknmi) than the most recent previously approved version (mizzi_knmi) on 2026-02-19, but loescornelisknmi 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.
v15.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (oyvindim) than the most recent previously approved version (onetrium) on 2026-02-05, 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.
v15.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (onetrium) than the most recent previously approved version (henrikj_) on 2026-01-22, 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.
v14.5.2
2 findingsThis version was published by a different npm account (henrikj_) than the most recent previously approved version (mizzi_knmi) on 2026-01-13. It has since remained available on npm for 190 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.