spatial-join-sanity — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited spatial-join-sanity (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.
A spatial join is where CRS bugs, geometry bugs, and cardinality bugs all converge. Do it deliberately.
crs-discipline) and have valid geometry (see validate-geometry). A spatial join across mismatched CRSs returns wrong matches with no error.within / containsintersectstouchesST_DWithin, near) — not intersects, and not a post-hoc distance filter.A spatial join is one-to-many. A point on a shared border matches both polygons; overlapping polygons multiply rows. Decide explicitly:
Don't let the join silently change your record count.
Compare input vs output row counts and state it. If a 10,000-point layer becomes 14,000 rows after a join to polygons, that's a boundary/overlap multiplication that needs an explanation — not something to hand over unnoticed. A point count that drops means unmatched features fell out of an inner join; decide whether that's intended.
Spatial joins produce a table that looks normal whether or not it's correct. The errors — wrong predicate, CRS mismatch, silent row multiplication — don't surface as crashes; they surface as a deliverable with the wrong counts. A predicate chosen on purpose and a row-count check catch them before they ship.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.