next-safe-ts
Advanced tools
This fork supports next 14, converts to typescript, gets test coverage up to 100%.
This fork supports next 14, converts to typescript, gets test coverage up to 100%.
It'll also error if you use none or * on a permissions-policy along with other values.
next-safe
next-safe helps secure your Next.js apps by providing sensible defaults for the most common security headers, including:
Content-Security-PolicyPermissions-Policy (formerly known as Feature-Policy)Referrer-PolicyX-Content-Type-OptionsX-Frame-OptionsCheck out the full documentation at https://trezy.gitbook.io/next-safe.
Thanks goes to these wonderful people (emoji key):
 Trezy 🐛 💻 💡 🤔 🚇 🚧 👀 ⚠️ |  Cameron Welter 🐛 💻 🤔 🚧 ⚠️ |  Omar López 📖 |  Anton Frattaroli 🐛 |  april-ctrlspire 🤔 |  João Lucas Evangelista C. de Amorim 🐛 💻 |  anvelicon 💻 📖 🤔 |
This project follows the all-contributors specification. Contributions of any kind welcome! Check out our contributing docs for help getting started!
FAQs
This fork supports next 14, converts to typescript, gets test coverage up to 100%.
We found that next-safe-ts demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Malicious PyPI checkers validate stolen emails against TikTok and Instagram APIs, enabling targeted account attacks and dark web credential sales.
Security News
The Node.js TSC opted not to endorse a feature bounty program, citing concerns about incentives, governance, and project neutrality.
Research
Security News
A look at the top trends in how threat actors are weaponizing open source packages to deliver malware and persist across the software supply chain.