Nothing here runs on your machine. This repository publishes prose, screenshots and a claims register — no package, no install line, no dependency to resolve. There is no supply chain here to compromise. That is a property of what is published today, not a promise about later: if the reading surface is ever packaged, this file changes with it.

The real exposure runs the other way — something of ours leaking into what we publish. A text guard scans every published page for internal names and toolchain paths before each publication, and it blocks. It does not read images. No script opens a screenshot on our behalf, and these screenshots are of a live workspace. That gap is declared here rather than quietly carried.

So the report that matters most on this repository is: a path, a hostname, a key or a person's name legible in one of the screenshots, or in a page.

• Not sensitive: open an issue, as usual.
• Sensitive: open an issue naming only which file, and that it is sensitive — no detail, no crop, no transcription. A private channel gets opened from there, and the detail goes in it.

No bounty, no response-time promise, and one maintainer. What there is: a report of that kind is treated as the most serious class of defect the repository can have, because it is the only one that costs someone other than us.