getsentry / getsentry/sentry

Support Integrity Policy violation reports

Open
#124,388 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Sentry’s Security Header endpoint accepts Reporting API payloads, but Relay currently classifies only legacy CSP reports and Reporting API reports with type: "csp-violation". Reports with type: "integrity-violation" are rejected as unsupported.

This prevents projects expanding Subresource Integrity coverage from ingesting, grouping, and surfacing policy violations in Sentry.

via ADV.

--

View Junior Session [Sentry]

Contributor guide

Open the 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.

Research direction

Start in relay-event-schema/src/protocol/security_report.rs and compare the existing Csp and Unsupported classification paths. Review the linked Sentry security policy reporting documentation and trace how accepted reports are ingested, grouped, and surfaced. Done means integrity-violation reports containing the listed fields are accepted and documented alongside CSP reports.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
70/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.