Security
Reporting a vulnerability
Report security bugs to shain.singh@owasp.org or through GitHub’s private vulnerability reporting: Report a vulnerability. Never open a public issue for an unreported vulnerability. Reports may go encrypted to the project’s OpenPGP key (9CB1781DC2BB28D37A0155DCAAF8226F3F4C1712); advisory text and key material live in SECURITY.md.
What counts as a security bug here
- Read-only invariant regression — any path that writes to traffic, injects, or terminates connections. The tap changes no path.
- Ledger chain integrity — appends without the
prevhash, rewrites of prior segments, or access-log under-capture. - eBPF surface regression — unpinned probe bytecode, capability escalation beyond the documented set.
- Data-minimization regression — arguments, prompts, or payload content stored by default; attributed mode on without explicit opt-in.
- Classification misstatement — verdicts or evidence that misstate an observation.
Repository hygiene
Secret scanning and push protection stay on; every commit carries a signature; Dependency Review checks licence and vulnerability deltas on every pull request.