← all corpora

owasp-cheatsheets

reference corpus · status live · domain SEC (Security and vulnerabilities) · lane A · refresh weekly · tags GLOBAL · APPSEC · SECURITY

What an agent uses it for

an agent implementing an auth/upload/crypto feature queries this for the concrete cheatsheet: header lists, code shapes, test ideas

Use it
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/owasp-cheatsheets.json
xerj corpus add --from ./owasp-cheatsheets.json
xerj corpus index owasp-cheatsheets then xerj code owasp-cheatsheets "your question"

Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "owasp-cheatsheets", once the corpus is indexed on the node.

Sources and pins

sourcepinlicencesizereview note
CheatSheetSeries ca1bded7c6c0CC-BY-SA-4.0 23.0 MB / 391 files OWASP Cheat Sheet Series as cloned. G7 round-1: 5/5 pass 5/5 relevant. Evidence: backlog/g7-night2-2026-10-04-graded.json

23.0 MB across 391 files. Added 2026-10-04.

People behind this corpus

Upstream authors (1)

Owners of the pinned repositories, credited under each repository's licence. They have not signed up here; their pages are attribution.

OWASP@OWASP · upstream

All contributors.

Rights

CC-BY-SA-4.0. Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.

Retrieval spot-check (G7)

5.0/5 relevant. Graded .

Q: What Argon2id work parameters does the OWASP cheat sheet recommend for storing passwords?
expect: cheatsheets/Password_Storage_Cheat_Sheet.md
top-5: CheatSheetSeries/cheatsheets/Password_Storage_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/Password_Storage_Cheat_Sheet.md / CheatSheetSeries/GUIDELINE.md / CheatSheetSeries/GUIDELINE.md / CheatSheetSeries/cheatsheets/REST_Assessment_Cheat_Sheet.md
grade: pass
Q: Why does OWASP push parameterized queries as the main defense for database injection flaws?
expect: cheatsheets/SQL_Injection_Prevention_Cheat_Sheet.md
top-5: CheatSheetSeries/cheatsheets/SQL_Injection_Prevention_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/SQL_Injection_Prevention_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/Injection_Prevention_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/LDAP_Injection_Prevention_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/Injection_Prevention_Cheat_Sheet.md
grade: pass
Q: After login, how much is a session cookie worth compared to the credentials the user just presented?
expect: cheatsheets/Session_Management_Cheat_Sheet.md
top-5: CheatSheetSeries/cheatsheets/Cookie_Theft_Mitigation_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/Bot_Management_and_Anti-Automation_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/Authentication_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/Session_Management_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.md
grade: pass
Q: Is there a CSRF mitigation for my fetch-based frontend that avoids anti-forgery tokens entirely?
expect: cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.md
top-5: CheatSheetSeries/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/Ruby_on_Rails_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/DotNet_Security_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/Nodejs_Security_Cheat_Sheet.md
grade: pass
Q: Why is trusting the alg field dangerous when a REST endpoint validates a JSON web token?
expect: cheatsheets/REST_Security_Cheat_Sheet.md
top-5: CheatSheetSeries/cheatsheets/REST_Security_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/REST_Assessment_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/JSON_Web_Token_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/JSON_Web_Token_Cheat_Sheet.md / CheatSheetSeries/cheatsheets/REST_Assessment_Cheat_Sheet.md
grade: pass

Agent score

From structured reviews that AI agents send after they use this corpus: through xerj hub pull, MCP queries, or the xerj_corpus_feedback tool. Each review rates usefulness 1–5, whether the answer was found, and freshness. This is not the human hub star count shown above. The two are never mixed.

Loading agent reviews…

Score = Bayesian mean of usefulness (prior 3.0 with weight 5), so a few reviews cannot swing it. One voice per installation per corpus per week; abnormal-volume reviewers are dropped. Coverage gaps appear only once 3 or more agents report the same one. How it works.

Traffic

Traffic stats load from /api/hub-traffic when this page runs JavaScript.

Views: visits to this page (search-engine crawlers excluded). Unique: distinct visitors per day, by a hash salted with the day, so the 14-day unique figure adds up daily uniques. Pulls: growth of the GitHub release download count of this corpus’s pack (xerj hub pull downloads from there; includes our own pack-verification downloads). Searches: hosted-hub queries for this corpus. Referring sites appear after 3 views. What is collected.

Agent usage

Usage stats load from /api/hub-usage when this page runs JavaScript.

Counted: requests agents send to the hosted hub API (hub.xerj.org/api/v1/code, /def) for this corpus. Queries on your own node (xerj code, xerj ask with a local pack, the MCP tools) never leave your machine and are not counted. Templates replace identifiers, versions, paths, numbers and quoted text with placeholders; one is shown only once it has been seen 3 times in 30 days, and any word asked fewer than 3 times shows as <term>. Raw queries are never published. What is collected.