← Home

@opengeoweb/snackbar

npm Repository Homepage
18
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
provenance publisher-changed AI (provenance): henrikj_ is an established publisher within the @opengeoweb org with 5 approved packages; transition appears legitimate. ai
maintainer-change maintainer-added AI (maintainer-change): Bulk maintainer update consistent with org-level team restructuring, not a hostile takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of btorrente paired with new team members; no malicious indicators. ai
phantom-deps phantom-dep:react-i18next AI (phantom-deps): i18n dep used via config pattern; stable FP for this package. ai
phantom-deps phantom-dep:@reduxjs/toolkit AI (phantom-deps): Redux toolkit used via config/store pattern; stable FP for this package. ai
phantom-deps phantom-dep:i18next AI (phantom-deps): Declared as runtime dep, used via config/peer pattern in component library; stable FP for this package. ai
phantom-deps phantom-dep:@opengeoweb/shared AI (phantom-deps): Same-org sibling dep; phantom-dep is a FP for this monorepo package. ai
phantom-deps phantom-dep:@opengeoweb/theme AI (phantom-deps): Same-org sibling dep; phantom-dep is a FP for this monorepo package. ai
phantom-deps phantom-dep:react-redux AI (phantom-deps): Same pattern — declared dep used indirectly via config in component library. ai
phantom-deps phantom-dep:@mui/material AI (phantom-deps): MUI is a core UI dep for this component library; phantom-dep is a FP here. ai

Versions (showing 18 of 18)

Version Deps Published
18.0.0 7 / 1
17.3.0 7 / 1
17.2.0 7 / 1
17.1.0 7 / 1
17.0.1 7 / 1
17.0.0 7 / 1
16.0.0 7 / 1
15.3.0 7 / 1
15.2.0 7 / 1
15.1.0 7 / 1
15.0.0 7 / 1
14.5.2 7 / 1
14.5.1 7 / 1
14.5.0 7 / 1
14.4.0 7 / 1
14.3.0 7 / 1
14.2.2 7 / 1
14.2.1 7 / 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: mizzi_knmi → 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: mizzi_knmi → 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

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.

v15.3.0

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

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

2 findings
HIGH Publisher changed: ernstdevreede → mizzi_knmi (on 2026-01-09) provenance

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

2 findings
HIGH Publisher changed: ernstdevreede → mizzi_knmi (on 2026-01-08) provenance

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

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.