Lower Haiku relevance concurrency for default Bedrock quota Two changes targeting the Haiku throttling (retries hitting 4/5 and 5/5 on the default account quota): - asvs_bundle had the same bug asvs_audit originally had: its Haiku relevance filter_batch was gated by sonnet_semaphore (5-wide) with no stagger, so it fired Haiku calls 5-at-once into the same instant. Give it a dedicated haiku_semaphore (default 2) and the same jittered startup stagger audit uses. - Lower asvs_audit HAIKU_CONCURRENCY default 3 -> 2 to match. Both tunable via the HAIKU_CONCURRENCY env var; raise after a Bedrock quota increase. This reduces collisions but does NOT raise the ceiling — on default quota a quota-increase request is still the real fix, and HAIKU_CONCURRENCY=1 is the most aggressive software lever.
AI-driven security auditing and code review for ASF projects
Automated OWASP ASVS v5.0.0 compliance auditing for any GitHub-hosted codebase. Downloads source code, discovers the architecture, runs per-requirement security analysis with Claude, and produces a consolidated report with deduplicated findings and GitHub issues. In production — piloted on ATR and Apache Steve.
Automated security scan of GitHub Actions workflows across an entire GitHub organization. Combines LLM classification (which repos publish what, where) with static pattern matching (12 check types from CRITICAL to INFO) to identify exploitable workflows, supply chain risks, and policy violations. Scanned 2,500+ Apache repos.
Both pipelines run on Gofannon — see docs/gofannon for platform setup.
├── ASVS/ # ASVS security audit pipeline │ ├── agents/ # Pipeline agent code (6 agents) │ ├── audit_guidance/ # Project-specific false positive guidance │ ├── reports/ # Audit output organized by project and commit │ └── rerun-sections.sh # QA: re-run failed sections, re-consolidate ├── gha-review/ # GitHub Actions security review │ ├── agents/ # Review pipeline agents (7 agents + tests) │ └── reports/ # Review output ├── docs/ │ ├── gofannon/ # Gofannon setup and agent development guide │ ├── tooling/ # Security tooling landscape and comparisons │ ├── roadmap/ # Eval framework, multi-spec expansion plans │ └── how-to-contribute.md └── util/ # Utility scripts
Mailing list: Say hello at 📧 dev@tooling.apache.org (Subscribe by sending an email with empty subject and body to dev-subscribe@tooling.apache.org and replying to the automated response, per the ASF mailing list how-to)
Slack: #tooling-discuss on the ASF Slack
Issues: Use GitHub Issues to ask questions, suggest approaches, or report bugs
Note: Please introduce yourself on the mailing list before submitting a PR; this helps us deter spam and means your contribution won't be overlooked.
This project is licensed under the Apache License 2.0.
Part of the Apache Tooling Initiative.