ogr2ogr-recipes — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ogr2ogr-recipes (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
ogr2ogr is the fastest way to move vector data around — and easy to get subtly wrong. Use the known-good patterns.
-t_srs EPSG:xxxx transforms to a target CRS.-s_srs EPSG:yyyy sets the source CRS — needed when the source CRS is undefined or wrong. Setting -s_srs does not move coordinates; only -t_srs transforms them. (This is the define-vs-project distinction; see crs-discipline.)-f GPKG) over shapefile: no 2 GB limit, no 10-character field-name truncation, no .dbf encoding surprises, multiple layers in one file.-nlt PROMOTE_TO_MULTI to avoid "mixed single/multi geometry" failures when a layer has both.ogr2ogr -f PostgreSQL "PG:host=... dbname=... user=..." input.gpkg \
-nln schema.table -nlt PROMOTE_TO_MULTI -lco GEOMETRY_NAME=geom -lco FID=id-where "status = 'active'"-spat xmin ymin xmax ymax-clipsrc clip.gpkgogrinfo -so <file> first to confirm layer name, CRS, geometry type, and feature count — and again after, to verify.-makevalid repairs geometry in transit; use -skipfailures only when you understand what's being skipped (and report how many).A guessed ogr2ogr command often "succeeds" while silently truncating field names, dropping the CRS, mangling encoding, or skipping features. The recipes above make the common conversions correct and verifiable instead of hopeful.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.