I built an open-source quality and regression linter for GeoJSON - would love feedback from people running production GIS pipelines

I've been working on a lot of mapping web apps as of late and have wanted something that could tell me a bit more than whether a GeoJSON file was technically valid. After rolling my own custom scripts for awhile, I ultimately decided to create a tool for this called GeoLint.

It's an open-source TypeScript/Node CLI and library, focusing on data quality (ex. inconsistent property types, duplicate or missing feature IDs), budgets (ex. enforcing limits on file size and feature count), and regression (comparing changes to GeoJSON files against an approved baseline). You can run it manually, or hook it into your CI/CD pipeline to run automatically when you push changes.

I put a fair amount of work into large-file performance, and I took a cue from ESLint and made GeoLint use workers when linting multiple files to tackle things in parallel and get the work done faster. Based on my benchmarks, it's pretty quick!

It's currently at 0.1.x, and I'm going to keep plugging away at it. I'm interested in feedback from folks who work with GeoJSON files regularly. Does this solve any problems you actually in encounter in GIS/data pipelines? Are there artifact-level mistakes or regressions you'd want a tool like this to flag that it doesn't today?

Repo link: https://github.com/jajego/geolint

npm link: https://www.npmjs.com/package/@jajego/geolint

Thanks, and happy Monday !