@mapbox/geojsonhint
validate and sanity-check geojson files
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): The 'takeover' reflects Mapbox org adding their full employee roster as maintainers on their scoped package — a known org management pattern, not a hostile takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Original author tmcw transferred the package to Mapbox org; ingalls (publisher) has a strong track record of 100 approved packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Mass addition of Mapbox employees is consistent with org-level npm maintainer management for @mapbox scoped packages. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from mapbox-npm-02 to mapbox-npm-07 occurred in 2019 and is a routine Mapbox internal account rotation. mapbox-npm-07 has a strong track record (72 approved packages). | ai | |
| phantom-deps | phantom-dep:vfile | AI (phantom-deps): vfile is used in the CLI bin script, not the main library entry point. This is a legitimate usage pattern for CLI tooling. | ai | |
| phantom-deps | phantom-dep:vfile-reporter | AI (phantom-deps): vfile-reporter is used in the CLI bin script, not the main library entry point. This is a legitimate usage pattern for CLI tooling. | ai | |
| phantom-deps | phantom-dep:minimist | AI (phantom-deps): minimist is a standard CLI argument parser used in the bin script; phantom-dep detection may not trace CLI usage paths correctly. | ai | |
| phantom-deps | phantom-dep:text-table | AI (phantom-deps): text-table is used in the CLI bin script for formatted output; phantom-dep detection may not trace CLI usage paths correctly. | ai | |
| phantom-deps | phantom-dep:concat-stream | AI (phantom-deps): concat-stream is used in the CLI bin script for stdin handling; phantom-dep detection may not trace CLI usage paths correctly. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is used in the CLI bin script for colored output; phantom-dep detection may not trace CLI usage paths correctly for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 6 / 6 | |
| 3.2.0 | 5 / 6 | |
| 3.1.1 | 5 / 6 | |
| 3.1.0 | 6 / 6 | |
| 3.0.2 | 6 / 6 | |
| 3.0.1 | 5 / 6 | |
| 3.0.0 | 5 / 6 | |
| 2.2.0 | 5 / 6 | |
| 2.1.0 | 5 / 6 | |
| 2.0.0 | 5 / 6 |
v3.3.0
2 findingsThis version was published by a different npm account than previous versions on 2023-11-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsThis version was published by a different npm account than previous versions on 2023-06-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
2 findingsThis version was published by a different npm account than previous versions on 2023-03-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2022-08-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsThis version was published by a different npm account than previous versions on 2022-08-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsThis version was published by a different npm account than previous versions on 2021-05-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2019-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-26. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.0
4 findingsAll previous maintainers (tmcw) were replaced by new maintainers (1ec5, aaaandrea, aag6z, aarthykc, ajashton, akit, alianthes, aliceykuo, alinapaz, allierowan, alulsh, amishas157, ampetr89, amyleew, anandthakker, andygol, angela.navarro, ansis, aparlato, apavani, apendleton, arunasank, asheemmamoowala, atevans-mapbox, benjamintd, bhousel, bkowshik, boblannon, brendanmcfarland, brsbl, brunoabinader, bsrinivasa, bsudekum, camillacaros, camilo.sanin, cammace, captainbarbosa-mbx, caseymm, castledoor, charloyd, chaupow, chetangowda, chriscx, chrisloer, cknouss, cmtoomey, colleenmcginnis, d-prukop, danieljh, danmactough, danpat, danpaz-mb, danswick, dasulit, davidtheclark, deniskoronchik, dgearhart, dhcole, dianeschulze, dnesbitt, dnomadb, dputtick, drboyer, dthompson, edgar-marca, electrostat, elifitch, emilymcafee, emilymdubois, enf, ericdeveloper, eschow, fa7c0n, fabianguerra, flippmoke, franka, freenerd, friedbunny, geografa, ghoshkaj, gknisely, gretacb, guardiola31337, heyadam_mapbox, heystenson, hjudge, ian29, ianshward, ilyasaf, ingalls, isiyu, ivovandongen, jacquestardie, jayana, jc-clark, jcsg, jfirebaugh, jim-martin, jinnycho503, jjanczyszyn, jmkiley, jordanwebb, jothirnadh, jrpruit1, juliannebg, k-mahoney, kaibot3000, kalimar, karenell, karenzshea, katydecorah, kdiluca, kellyoung, kepta, kevinkreiser, kilatsat, kkaefer, l-r, langstonsmith, lbud, lily-chai, lingoded, lizziegooding, lobenichou, lshig, lucaswoj, luiswalter, lukasmartinelli, lukaspaczos, lxbarth, lyzidiamond, macro-shen, maikyon, mal-wood, maning, manoharuss, mapbox-admin, mapsam, markmisener, mateov, matt.gosline, mattficke, mcwhittemore, miccolis, mikelmaron, millzpaugh, mollymerp, morgane, morganherlocker, mourner, msirenko, mtirwin, nammala, natslaughter, nickcordella, nickidlugash, nickitaliano, nikhilprabhakar, nmargolis, norchard, normanb, oini, okoriep, oliikit, oormilavinod, otherwiseman, oxidase, paigemoody, pdgoodman, perrygeo, peterqliu, planemad, poornibadrinath, pratikyadav, pt-44, pveugen, rasagy, rclark, rcleedev, recursivefunk, rmrice, ryan-baumann, s-heisler, sabaelhilo, sabzo, sadiew, saikia.abhishek, samanbb, samely, samfader, sbma44, scottschultz, scottsfarley93, sgillies, springmeyer, srividyacb, tapasweni-pathak, taziam, tcql, themarex, tmpsantos, tony-cj, tridip1931, tristen, upendrayadav, vakila, vincents, virginiayung, vladimir.kananovich, willwhite, xianny, yhahn, yuffster, yuletide, zmully, zugaldia, zurihunter92). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ingalls.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-03-16. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.