← Home

@opengeoweb/time-series

npm Repository Homepage

GeoWeb time-series library for the opengeoweb project

18
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.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): haavardso is an established publisher in the same org with 42 approvals; transition appears legitimate. ai
phantom-deps phantom-dep:@opengeoweb/shared AI (phantom-deps): Same-org monorepo package; heuristic false positive stable across versions. ai
phantom-deps phantom-dep:@opengeoweb/webmap AI (phantom-deps): Same-org monorepo package; heuristic false positive stable across versions. ai
phantom-deps phantom-dep:@opengeoweb/snackbar AI (phantom-deps): Same-org monorepo package; heuristic false positive stable across versions. ai
phantom-deps phantom-dep:@opengeoweb/form-fields AI (phantom-deps): Same-org monorepo package; heuristic false positive stable across versions. ai
phantom-deps phantom-dep:@opengeoweb/webmap-react AI (phantom-deps): Same-org monorepo package; heuristic false positive stable across versions. ai
phantom-deps phantom-dep:@tanstack/react-query AI (phantom-deps): Config-referenced peer dep in monorepo; stable false positive. ai
phantom-deps phantom-dep:@turf/turf AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:react-redux AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:react-window AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:@mui/material AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:react-i18next AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:@opengeoweb/api AI (phantom-deps): Intra-org sibling; stable false positive for this monorepo package. ai
phantom-deps phantom-dep:@opengeoweb/core AI (phantom-deps): Intra-org sibling; stable false positive for this monorepo package. ai
phantom-deps phantom-dep:@reduxjs/toolkit AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:react-sortablejs AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:@opengeoweb/store AI (phantom-deps): Intra-org sibling; stable false positive for this monorepo package. ai
phantom-deps phantom-dep:@opengeoweb/theme AI (phantom-deps): Intra-org sibling; stable false positive for this monorepo package. ai
phantom-deps phantom-dep:echarts-for-react AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:react-hook-form AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:msw AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:uuid AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:immer AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:echarts AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:i18next AI (phantom-deps): Monorepo component; deps declared for bundling, not direct import in dist. ai
phantom-deps phantom-dep:@types/geojson AI (phantom-deps): @types/geojson is a TypeScript type package used by convention in geospatial libs; stable false positive for this package. ai

Versions (showing 18 of 18)

Version Deps Published
18.0.0 26 / 1
17.3.0 26 / 1
17.2.0 26 / 1
17.1.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

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

2 findings
HIGH Publisher changed: karricgi → karoliinahautala (on 2026-04-29) provenance

This version was published by a different npm account than previous versions on 2026-04-29. 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.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

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

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.2

2 findings
HIGH Publisher changed: mizzi_knmi → henrikj_ (on 2026-01-13) provenance

This version was published by a different npm account than previous versions on 2026-01-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.

v14.5.1

1 finding
LOW No provenance attestation provenance

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

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