Add Web Security section and secure (HTTP security headers)

[cak]

Project

secure

Checklist

• One project per PR
• PR title format: Add project-name
• 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.