Proposal: Add Optional Content-Security-Policy (CSP) Header Support

Open
#48 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
security

Research direction

No files, tests, or entry points are named in the issue. Before work starts, clarify the policy, configuration mechanism, affected request path, and acceptance tests; what counts as done cannot be determined from the current proposal.

Written by the indexing model from the issue text.

Description

Hi @AlemTuzlak,

I’d like to contribute to the project by adding support for a default Content-Security-Policy (CSP) header — turned off by default, but easy to enable when needed.

What I propose:

  • Add CSP header support with a sensible default policy (e.g., default-src 'none')
  • Make it opt-in via an env variable or config flag

Happy to follow your preferred coding style or integration pattern. Let me know if you’re open to this — I can start working on a pull request right away.

Thanks!

Duncan

Dominant language
TypeScript
Stars
368
Forks
68
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from code-forge-io/base-stack

All issues in code-forge-io/base-stack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.