Entry format: - [project-name](url) - Description ending with period.
Description is concise and short
Why This Project Is Awesome
Which criterion does it meet? (pick one)
Industry Standard
Rising Star
Hidden Gem
Explain:
secure addresses a common but under-served problem: HTTP security headers are often scattered across routes, hooks, or framework-specific code, leading to drift and inconsistencies over time.
It provides a focused, minimal API for centralizing header policy and applying it consistently using ASGI and WSGI middleware. The project is actively maintained and designed for real-world usage across frameworks like FastAPI and Flask.
How It Differs
Most existing approaches rely on per-route configuration or framework-specific helpers. secure takes a middleware-first approach, allowing header policy to be defined once and applied at the application level.
This makes it easier to keep policies consistent and update them over time, especially for headers like CSP.
Notes
Adds a Web Security subcategory under Security to group application-layer web security tools.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/vinta/awesome-python/pull/3090
**Author:** [@cak](https://github.com/cak)
**Created:** 4/24/2026
**Status:** ✅ Merged
**Merged:** 4/24/2026
**Merged by:** [@JinyangWang27](https://github.com/JinyangWang27)
**Base:** `master` ← **Head:** `master`
---
### 📝 Commits (1)
- [`e386fbb`](https://github.com/vinta/awesome-python/commit/e386fbb0e6d7959cdec9943a829bbceb4e6591c0) add Web Security section and secure
### 📊 Changes
**1 file changed** (+7 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+7 -0)
</details>
### 📄 Description
## Project
[secure](https://github.com/TypeError/secure)
## Checklist
- [x] One project per PR
- [x] PR title format: `Add project-name`
- [x] Entry format: `- [project-name](url) - Description ending with period.`
- [x] Description is concise and short
## Why This Project Is Awesome
Which criterion does it meet? (pick one)
- [ ] **Industry Standard**
- [ ] **Rising Star**
- [x] **Hidden Gem**
Explain:
secure addresses a common but under-served problem: HTTP security headers are often scattered across routes, hooks, or framework-specific code, leading to drift and inconsistencies over time.
It provides a focused, minimal API for centralizing header policy and applying it consistently using ASGI and WSGI middleware. The project is actively maintained and designed for real-world usage across frameworks like FastAPI and Flask.
## How It Differs
Most existing approaches rely on per-route configuration or framework-specific helpers. secure takes a middleware-first approach, allowing header policy to be defined once and applied at the application level.
This makes it easier to keep policies consistent and update them over time, especially for headers like CSP.
## Notes
Adds a Web Security subcategory under Security to group application-layer web security tools.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/vinta/awesome-python/pull/3090
Author: @cak
Created: 4/24/2026
Status: ✅ Merged
Merged: 4/24/2026
Merged by: @JinyangWang27
Base:
master← Head:master📝 Commits (1)
e386fbbadd Web Security section and secure📊 Changes
1 file changed (+7 additions, -0 deletions)
View changed files
📝
README.md(+7 -0)📄 Description
Project
secure
Checklist
Add project-name- [project-name](url) - Description ending with period.Why This Project Is Awesome
Which criterion does it meet? (pick one)
Explain:
secure addresses a common but under-served problem: HTTP security headers are often scattered across routes, hooks, or framework-specific code, leading to drift and inconsistencies over time.
It provides a focused, minimal API for centralizing header policy and applying it consistently using ASGI and WSGI middleware. The project is actively maintained and designed for real-world usage across frameworks like FastAPI and Flask.
How It Differs
Most existing approaches rely on per-route configuration or framework-specific helpers. secure takes a middleware-first approach, allowing header policy to be defined once and applied at the application level.
This makes it easier to keep policies consistent and update them over time, especially for headers like CSP.
Notes
Adds a Web Security subcategory under Security to group application-layer web security tools.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.