Thanks for your interest in contributing! π
python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -r requirements.txt- Run the test suite:
pytest -q - Keep it passive: this is a zero-touch tool β no outbound probes may be added.
- Fail closed: any new data source must respect the compliance guardrail.
- Use conventional commits:
feat:,fix:,docs:,chore:,test: - Keep each commit focused on a single intent
- Reference issues where applicable
- Avoid committing secrets β run
gitleaks detectbefore pushing (CI will block leaks)
- Tests pass locally
- No secrets or API keys committed
- Docs updated if behavior changed
- New data source connectors include
fail-closedcompliance handling
Include: command used, expected vs actual output, and whether the target is reachable from your network (the tool may be blocked by network policies).