π‘οΈ Sentinel: Add standard security headers #50
+31
β0
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.
π‘οΈ Sentinel: [HIGH] Add standard security headers
π¨ Severity: HIGH
π‘ Vulnerability: Missing HTTP security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options) left the application vulnerable to common web attacks like clickjacking and MIME sniffing.
π― Impact: Attackers could potentially frame the application (if it had a UI), sniff content types to execute malicious scripts, or downgrade HTTPS connections.
π§ Fix: Implemented a middleware in
src/http-transport.tsthat sets these headers on every response. HSTS is conditionally applied only to non-localhost connections to support local development.β Verification: Verified manually with
src/security-headers.test.ts(created during development) and by running the full test suite to ensure no regressions. Usecurl -I <url>to verify headers in production.PR created automatically by Jules for task 2736432306536903865 started by @davidruzicka