@mapbox/mapbox-gl-style-spec
a specification for mapbox gl styles
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Both accounts are Mapbox org publishers with strong approval histories; internal account rotation pattern. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 14.26.0 | 6 / 0 | |
| 14.25.0 | 7 / 0 | |
| 14.24.1 | 9 / 0 | |
| 14.24.0 | 9 / 0 | |
| 14.23.0 | 9 / 0 | |
| 14.22.0 | 9 / 0 | |
| 14.21.0 | 10 / 0 | |
| 14.20.0 | 10 / 0 | |
| 14.19.1 | 10 / 0 | |
| 14.19.0 | 10 / 0 | |
| 14.18.1 | 10 / 0 | |
| 14.18.0 | 10 / 0 | |
| 14.17.0 | 10 / 0 | |
| 14.16.1 | 10 / 0 | |
| 14.16.0 | 10 / 0 | |
| 14.15.0 | 10 / 0 | |
| 14.14.0 | 10 / 0 | |
| 14.13.0 | 10 / 0 | |
| 14.12.0 | 10 / 0 | |
| 14.11.0 | 10 / 0 | |
| 14.10.0 | 10 / 0 | |
| 14.9.2 | 10 / 0 | |
| 14.9.1 | 10 / 0 | |
| 14.9.0 | 10 / 0 | |
| 14.8.0 | 10 / 0 | |
| 14.7.1 | 10 / 0 | |
| 14.7.0 | 10 / 0 | |
| 14.6.0 | 10 / 0 | |
| 14.5.2 | 10 / 0 | |
| 14.5.1 | 10 / 0 | |
| 14.5.0 | 10 / 0 | |
| 14.4.0 | 11 / 0 |
v14.26.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mbx-npm-01-production) than the most recent previously approved version (mbx-npm-07-production) on 2026-07-09, but mbx-npm-01-production 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.
v14.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.