🛡️ Sentinel: [security improvement]

[seonghobae]

🚨 Severity: MEDIUM
💡 Vulnerability: Content-Security-Policy in index.html used base-uri 'self'. While slightly restrictive, it is overly permissive for a purely static site and could potentially allow base tag injection if an attacker could place a malicious file on the same origin.
🎯 Impact: Base tag injection can hijack relative links and form actions, potentially redirecting users to unintended paths or leaking form data.
🔧 Fix: Changed the CSP directive to base-uri 'none' which completely disables the use of the <base> tag.
✅ Verification: Added tests/test_index_security.py to continuously assert that base-uri 'none' is present and base-uri 'self' is not. Run pytest tests/test_index_security.py.

---

PR created automatically by Jules for task 5818972268557777314 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6ed30d7a-01bf-4ea2-afdb-66b341067a89

📥 Commits

Reviewing files that changed from the base of the PR and between d06c1cb and 228ff32.

📒 Files selected for processing (4)

• .jules/sentinel.md
• CHANGELOG.md
• index.html
• tests/test_index_security.py

---

_{Comment @coderabbitai help to get the list of available commands.}