AI-Assisted Secure Coding (Appendix C) · Adversarial AI Detection in Inbound Contributions
Flag unusual contribution patterns
Verify that contribution-velocity and contributor-reputation analytics flag anomalies: bulk PR creation from newly created accounts, coordinated fork waves immediately preceding PRs, PR volumes that are inconsistent with human authorship, and reuse of payload patterns across unrelated repositories.
OWASP AISVS v1.01, requirement AC.13.1
In plain English
Flag unusual contribution patterns, such as many PRs from new accounts, waves of forks before PRs, volumes no human could produce, and the same payloads across unrelated repositories.
What good looks like
- Contribution analytics run continuously.
- The listed anomalies raise flags.
- Flags are reviewed.
How teams usually do it
- Analytics on repository events with simple rules and thresholds.
Evidence an auditor would accept
- Rules and recent flags.
Common mistakes
- Only noticing a campaign after merges have happened.
Not sure which requirements apply to your system? Take the assessment.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.