am-i-hacked: venv integrity, dark-corner system scan, --max-findings, and review fixes

[IsaacBell]

am-i-hacked: Python virtualenv integrity, dark-corner system scan, --max-findings, and the fixes a security review of this branch turned up.

Added

• Python virtualenv integrity check in the folder scan, for every venv under the scanned folder: files that no longer match their RECORD hashes (HIGH), RECORD paths that leave the venv or pass through a symlinked folder (HIGH, never opened), files and symlinks no package owns, console scripts no package claims (each venv on its own claims), RECORD entries with no hash, venvs whose RECORD files were deleted, and code-running .pth and sitecustomize hooks.
• --system also scans a fixed list of places where tooling installs code outside any project (venvs, uv/pip/npx caches, pyenv, pipx, pnpm, cargo, bun, deno, go, gem). Absent folders are skipped; unreadable ones are reported.
• --max-findings N (1 to 999999999, default 1000); the true total and per-rule counts print past the cap.
• The system scan reports a check it could not run instead of passing it: ps or codesign missing, a crontab -l error, an AI-tool config jq cannot parse, an unreadable dark corner, your own relative-path process lsof could not resolve.

Changed

• bin/host-audit.sh is now bin/system-scan.sh; host-audit.sh stays as a shim.
• Hex and unicode escape findings in installed dependency folders (site-packages, dist-packages, node_modules) are one summary line. vendor/ is committed code, so its findings are still listed.

Security fixes found in review

• A source file with one NUL byte was skipped as binary, hiding the whole file from the folder scan (also on main). Source files are now always read as text.
• A | in a RECORD console-script name could mark any planted bin/ script as claimed.
• A console-script claim in one venv hid a planted script of the same name in another.
• A RECORD path through a symlinked folder made the scanner read and hash a file outside the venv.
• Deleting every RECORD in a venv made it scan clean.
• Bin allowlist was a prefix match (python*, pip*), so python3-helper or pipx were skipped. It is now exact names, and an unclaimed pip is reported.
• Scanning a repo root reported every console script in its .venv as a HIGH "outside the package" finding.
• systemd/autostart Exec lines were glob-expanded; hook commands were cut at a tab; persistence scripts with a newline in the name were not read.
• --max-findings 08 hit bash octal parsing; 0 and unbounded values were accepted.

Every fix has a bats test, and each new test fails against the previous commit.

Docs

• Root README, package README and docs/llms.txt mark the dark-corner scan, venv integrity and --max-findings as the next release, so the published 2.0.1 is not misrepresented.
• secure-semgrep's ssrf loadout added to its README and docs.
• Landing page: npx run command per tool card, a plain line under the hero command, absolute canonical URL, SoftwareApplication JSON-LD with its author, and an author credit in the footer.
• Every README, llms.txt, the landing page and the skills say npx am-i-hacked (no trailing .; it scans the current folder) and npm install --save-dev.

Merge

Squash merge, please: the branch has an empty commit and several fix-up commits.