← Home

@opengeoweb/core

npm Repository Homepage
8
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:@reduxjs/toolkit AI (phantom-deps): Used via config/store setup in monorepo; phantom-dep heuristic fires on indirect usage patterns. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped monorepo package @opengeoweb/core; Levenshtein match to 'cors' is a false positive by namespace. ai
phantom-deps phantom-dep:@types/geojson AI (phantom-deps): Type-only package; not directly imported at runtime, stable false positive for this package. ai
phantom-deps phantom-dep:react-draggable AI (phantom-deps): Listed in package.json dependencies and referenced in config; phantom-dep heuristic misfires here. ai

Versions (showing 8 of 8)

Version Deps Published
17.2.0 27 / 1
17.0.1 27 / 1
16.0.0 27 / 1
15.2.0 27 / 1
14.4.0 28 / 1
14.3.0 26 / 1
14.2.2 26 / 1
14.2.1 26 / 1

v17.2.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@opengeoweb/core' is 1 edit(s) away from popular package 'cors'.

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 typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@opengeoweb/core' is 1 edit(s) away from popular package 'cors'.

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 typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@opengeoweb/core' is 1 edit(s) away from popular package 'cors'.

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.

v15.2.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@opengeoweb/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@opengeoweb/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@opengeoweb/core' is 1 edit(s) away from popular package 'cors'.

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. Consider requesting the maintainer enable provenance via CI/CD.

v14.2.1

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@opengeoweb/core' is 1 edit(s) away from popular package 'cors'.

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.