Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add security headers with Helmet

Abierto
  • ¿Algo no está bien?
#64 6 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@08abhinav ya está trabajando en esto.

Desde el 21/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

backend difficulty: easy enhancement good first issue hacktoberfest
Context

The API doesn't send the standard security headers that tell browsers to be careful with its responses (for example X-Content-Type-Options: nosniff). Helmet is the usual Express middleware for this: one dependency and a couple of lines.

✅ The helmet dependency is approved for this issue. Install it from the server/ folder (npm install helmet --prefix server) and commit both server/package.json and server/package-lock.json.

Files likely involved
  • server/src/app.js (the middleware section near the top)
  • server/package.json, server/package-lock.json
Acceptance criteria
  • app.use(helmet()) is added early in the middleware chain, before the routes, with a short comment saying what it does.
  • The frontend still works when it runs on a different address from the API (CORS), both locally and on the deployed site.
  • The README's API section mentions that security headers are sent.
How to test
  1. curl -i http://localhost:5000/api/v1/health: the response includes headers like X-Content-Type-Options: nosniff and X-Frame-Options.
  2. Run the whole app (npm run dev), log in, and create, edit and delete a task. Nothing is blocked, and there are no CORS errors in the browser console.
  3. npm test still passes.

New here? 👋 Good first issues are reserved for people making their first few open-source contributions. Comment below to ask to work on this issue, and wait to be assigned. Then follow CONTRIBUTING.md for setup and how to open a pull request. Questions are welcome in the comments or in Discussions.

Lenguaje dominante
JavaScript
Estrellas
3
Forks
2
Merge medio
7 h 8 min
PR fusionados (30 d)
38

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de KEX-03/taskflow

Todos los issues de KEX-03/taskflow

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.