owasp/cheatsheetseries

The OWASP Cheat Sheet Series was created to provide a concise collection of high value information on specific application security topics.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 59 minutes ago
Added to GitGenius on September 13th, 2026
Created on December 21st, 2018
Open Issues & Pull Requests: 62 (+0)
GitHub issues: Enabled
Number of forks: 4,619
Total Stargazers: 33,160 (+0)
Total Subscribers: 581 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.6 hours
Mean response time: 4.7 days
90th percentile: 6.9 days
Tracked items: 309

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 81% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 5% of issues opened in the past year have been closed. Three people close 90% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 36
New in 7 days: 3
Closed in 7 days: 1
Avg open age: 243 days
Stale 30+ days: 20
Stale 90+ days: 13

Recent activity

Opened in 7 days: 3
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • UPDATE_CS (181)
  • ACK_OBTAINED (176)
  • HELP_WANTED (127)
  • ACK_WAITING (81)
  • NEW_CS (64)
  • jules (5)
  • INTERNAL (3)
  • WEBSITE (1)

Detailed Description

OWASP Cheat Sheet Series is a reference collection of application security best practices organized as concise guides on specific topics.

The project addresses the need for developers to quickly access reliable security guidance when building applications. It provides focused cheat sheets covering individual security domains, allowing builders to reference established practices without extensive research. The content is maintained as markdown source files and published through an official website where users can read and reference the material.

Developers should use this resource when they need to understand security best practices for a particular application concern, whether during design, development, or code review. The project suits teams of any size looking for authoritative OWASP-backed guidance. The material is intended for reference through the official website rather than as embedded documentation in external sources.

The project maintains an active contribution process with a documented guide for adding new cheat sheets and improving existing content. The team actively invites contributors and encourages participation through multiple channels including a dedicated Slack community. The project supports local development and testing through Python-based build tooling, with options for both direct execution and containerized builds using Docker or Podman. Automated linting checks help maintain markdown quality and consistent terminology across the collection.