Private feedback

For feedback you can’t post in a public issue — testing on a private or internal codebase. Goes straight to the maintainer. Raw output and one concrete example beat polished prose. Prefer public? Open a GitHub issue instead.

Your email (so I can follow up — optional) Which parts did you use?

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

Language Domain roughly what kind of project — pick “Other” to type your own Domain — other if you picked “Other” above, or nothing fits, type it here Approximate lines of code rough 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 behavior, with a minimal repro Anything else? any other feedback, ideas, or context that didn’t fit above

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

plumb-line · github.com/slopstopper/plumb-line