← Home

ol

npm Repository Homepage
5
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ahocevartschaubfredj

Keywords

mapmappingopenlayers

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): 'ol' is the official OpenLayers package name, not a typosquat. ai
typosquat typosquat.levenshtein:got AI (typosquat): 'ol' is the official OpenLayers package name, not a typosquat. ai
typosquat typosquat.levenshtein:pg AI (typosquat): 'ol' is the official OpenLayers package name, not a typosquat. ai
typosquat typosquat.levenshtein:qs AI (typosquat): 'ol' is the official OpenLayers package name, not a typosquat. ai
typosquat typosquat.levenshtein:joi AI (typosquat): 'ol' is the official OpenLayers package name, not a typosquat. ai
typosquat typosquat.levenshtein:zod AI (typosquat): 'ol' is the official OpenLayers package name, not a typosquat. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get used in a standard Proxy trap handler in DOM utilities; not obfuscation. ai
phantom-deps phantom-dep:@types/rbush AI (phantom-deps): @types/rbush is a type-only dependency; not imported at runtime by convention. ai

Versions (showing 5 of 5)

Version Deps Published
10.9.0 6 / 0
10.8.0 6 / 0
10.7.2 5 / 0
10.7.1 6 / 0
10.7.0 5 / 0

v10.8.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.7.2

2 findings
HIGH Provenance attestation missing — previous versions had it provenance

This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.

INFO Publisher changed: GitHub Actions → ahocevar (on 2026-02-11, known maintainer) provenance

This version was published by a different npm account (ahocevar) than the most recent previously approved version (GitHub Actions) on 2026-02-11, but ahocevar 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.

v10.7.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.7.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.