Contributing - AwareXone Docs

PRs are welcome. Highest-value areas:

Contribution	Why
New scanner modules or detection techniques	Broader coverage
Payload additions to `skills/security-arsenal/SKILL.md`	Better bypass coverage
Methodology improvements backed by paid reports	Proven techniques only
Platform support (YesWeHack, Synack, HackenProof, …)	Wider program coverage
False-positive fixes with regression tests	Fewer N/A submissions

Before you start

Check open issues
One feature per PR
Run tests: pytest tests/
Scanner additions need a real PoC or real-world precedent — no theoretical-only detectors

Workflow

git clone https://github.com/YOUR_USERNAME/Agentic-Bug-Hunter.git
cd Agentic-Bug-Hunter
git checkout -b feat/your-contribution

# edit, then:
pytest tests/

git commit -m "feat: short description of what and why"
git push origin feat/your-contribution

Open a PR against Awarexone/Agentic-Bug-Hunter.

Commit prefixes

feat:  new capability
fix:   bug fix
docs:  documentation only
test:  adding or fixing tests
chore: maintenance (deps, CI, cleanup)

PR checklist

pytest tests/ passes
No hardcoded targets, API keys, or real domain names in code
Scanner additions use [CONFIRMED] / [POSSIBLE] / [INFORMATIONAL] confidence states
Methodology changes cite a real finding or public write-up

Conduct and security

Questions: GitHub Discussions or hello@awarexone.com.