01 / plumb-line · private feedback

Feedback you can't post in a public issue.

For testing on a private or internal codebase. Raw output and one concrete example beat polished prose: paste logs, don't summarise. Prefer a public record? Open a feedback issue instead.

Sent. Thank you. If you left an email, a reply may follow; there is no automatic acknowledgement.

Your email optional, so a follow-up is possible Which parts did you use?

Provenance library (mark / derive / auditMeta) no-provenance-bypass lint audit skill boundary adapter GitHub Action

Language Domain roughly what kind of project; pick "Other" to type your own Domain, other if you picked "Other", or nothing fits Approximate lines of code order of magnitude, e.g. "~20k" Version tested package version, or git tag / SHA What did it catch? a value that was un-provenanced, mock-leaked, or confidently wrong that plumb-line surfaced: before → after Lint output: false positives or missed cases paste the output; for each flag, correct or noise? did it miss a bypass you know of? Friction where did you get stuck: install, imports, wiring the lint, the API? docs wrong or confusing? Bugs / errors stack traces or surprising behaviour, with a minimal repro Anything else?

You may quote this feedback and name me as an early user.

Sending posts this form to Formspree, which processes it in the United States and delivers it to the slopstopper mailbox. Nothing is sent until you press the button. Details, retention and your rights: privacy notice.