fix: viewer security hardening and evolve write ordering#69
Conversation
- Viewer auth: use timing-safe HMAC comparison instead of string equality - Viewer HTML: add Content-Security-Policy header - Viewer POST/DELETE: validate Content-Type is application/json (415 on mismatch) - Evolve: supersede old memory before saving new to prevent dual-latest on partial failure
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe pull request reorders memory evolution write operations in the relations flow, then hardens the viewer server with security improvements: timing-safe authentication comparison, Content-Security-Policy headers, and Content-Type validation on POST and DELETE requests. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~22 minutes Possibly related PRs
Poem
✨ Finishing Touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Closes
Test plan
npm run buildpassesSummary by CodeRabbit
Release Notes