@mapbox/mapbox-gl-draw
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@mapbox/geojson-normalize | AI (phantom-deps): Same-org dep, likely used but missed by import scan. | ai | |
| phantom-deps | phantom-dep:@mapbox/geojson-area | AI (phantom-deps): Same-org dep, likely used but missed by import scan. | ai | |
| phantom-deps | phantom-dep:@mapbox/geojson-extent | AI (phantom-deps): Same-org dep, likely used but missed by import scan. | ai | |
| phantom-deps | phantom-dep:@mapbox/point-geometry | AI (phantom-deps): Same-org dep, likely used but missed by import scan. | ai | |
| phantom-deps | phantom-dep:hat | AI (phantom-deps): Common ID-gen dep, likely used internally; no malicious indicator. | ai | |
| phantom-deps | phantom-dep:xtend | AI (phantom-deps): Standard utility dep, false-positive prone heuristic. | ai | |
| phantom-deps | phantom-dep:lodash.isequal | AI (phantom-deps): Standard utility dep, false-positive prone heuristic. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Internal mode loader over fixed local files, not arbitrary input. | ai | |
| dependencies | unvetted-dep:@mapbox/geojson-normalize | AI (dependencies): First-party Mapbox utility; stable dependency of this package across versions. | ai | |
| dependencies | unvetted-dep:@mapbox/geojson-area | AI (dependencies): First-party Mapbox utility; stable dependency of this package across versions. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.5.1 | 6 / 20 | |
| 1.5.0 | 5 / 20 | |
| 1.4.3 | 7 / 27 | |
| 1.4.2 | 7 / 27 | |
| 1.4.1 | 7 / 27 | |
| 1.4.0 | 7 / 27 | |
| 1.3.0 | 7 / 37 | |
| 1.2.2 | 8 / 37 | |
| 1.2.0 | 9 / 35 | |
| 1.1.2 | 8 / 24 | |
| 1.1.1 | 8 / 24 | |
| 1.1.0 | 8 / 24 | |
| 1.0.9 | 8 / 24 | |
| 1.0.8 | 8 / 24 | |
| 1.0.7 | 8 / 24 | |
| 1.0.6 | 8 / 24 | |
| 1.0.5 | 8 / 24 | |
| 1.0.4 | 8 / 24 | |
| 1.0.3 | 8 / 24 | |
| 1.0.2 | 8 / 24 | |
| 1.0.1 | 8 / 24 | |
| 1.0.0 | 8 / 24 |
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
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 (mapbox-npm-07) than the most recent previously approved version (mapbox-npm-08) on 2023-09-21, but mapbox-npm-07 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.
v1.4.2
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 (mapbox-npm) than the most recent previously approved version (mapbox-npm-08) on 2023-06-28, but mapbox-npm 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.
v1.4.1
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 (mapbox-npm-02) than the most recent previously approved version (mapbox-npm-08) on 2023-02-14, but mapbox-npm-02 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.
v1.4.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 (mapbox-npm-04) than the most recent previously approved version (mapbox-npm-08) on 2023-01-31, but mapbox-npm-04 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.
v1.3.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 (mapbox-npm-08) than the most recent previously approved version (mapbox-npm-05) on 2021-05-20, but mapbox-npm-08 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.
v1.2.2
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 (mapbox-npm-08) than the most recent previously approved version (mapbox-npm-05) on 2021-02-25, but mapbox-npm-08 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.
v1.2.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 (mapbox-npm-05) than the most recent previously approved version (mapbox-npm-08) on 2020-07-13, but mapbox-npm-05 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.
v1.1.2
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 (mapbox-npm-06) than the most recent previously approved version (mapbox-npm-08) on 2019-05-22, but mapbox-npm-06 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.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.