ol-mapbox-style
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:boundlessgeo.com | AI (email-domain): Stale email from defunct company (Boundless Geo); package is under active openlayers org maintenance. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 13.4.1 | 2 / 40 | |
| 13.4.0 | 2 / 40 | |
| 13.3.0 | 2 / 40 | |
| 13.2.1 | 2 / 40 | |
| 13.2.0 | 2 / 40 | |
| 13.1.1 | 2 / 40 | |
| 13.1.0 | 2 / 40 | |
| 13.0.1 | 2 / 40 | |
| 13.0.0 | 2 / 40 |
v13.4.1
2 findingsMaintainer email '[email protected]' uses domain 'boundlessgeo.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.4.0
2 findingsMaintainer email '[email protected]' uses domain 'boundlessgeo.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.0
2 findingsMaintainer email '[email protected]' uses domain 'boundlessgeo.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.1
2 findingsMaintainer email '[email protected]' uses domain 'boundlessgeo.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.0
2 findingsMaintainer email '[email protected]' uses domain 'boundlessgeo.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.1
2 findingsMaintainer email '[email protected]' uses domain 'boundlessgeo.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.0
2 findingsMaintainer email '[email protected]' uses domain 'boundlessgeo.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.1
2 findingsMaintainer email '[email protected]' uses domain 'boundlessgeo.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
2 findingsMaintainer email '[email protected]' uses domain 'boundlessgeo.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.