Add secure library for consistent HTTP security headers in FastAPI#291
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
name: Add a new project
about: Suggest a new FastAPI project for the Awesome FastAPI list
title: "[NEW] secure"
Project Information
Project Name:
secure
Project URL:
https://github.com/TypeError/secure
Description:
A small library for defining and applying HTTP security headers consistently in FastAPI applications using ASGI middleware.
Criteria
Originally created several years ago and recently updated with a new v2 design focused on composability, middleware support, and safer header handling.
See release history:
https://github.com/TypeError/secure/releases
It addresses a common gap in FastAPI applications where HTTP security headers are defined inconsistently across middleware, response hooks, and handlers.
The library centralizes header configuration in a single object and applies it through ASGI middleware, making it easier to keep policies like CSP consistent as applications grow.
AI Disclosure
Additional Information
The project is intentionally small and dependency-free, with a focus on clarity and predictable behavior.
It supports both middleware-based integration and direct response usage, allowing it to fit naturally into existing FastAPI applications without requiring architectural changes.