Support Integrity Policy violation reports
Nobody has claimed this yet.
- 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.
Integrity-PolicyandIntegrity-Policy-Report-Onlyproduceintegrity-violationreports containingdocumentURL,blockedURL,destination, andreportOnly: https://developer.mozilla.org/en-US/docs/Web/API/IntegrityViolationReport- Current Sentry documentation describes CSP reporting only: https://docs.sentry.io/platforms/javascript/security-policy-reporting/
- Relay’s classifier has only
CspandUnsupportedreport types: https://github.com/getsentry/relay/blob/master/relay-event-schema/src/protocol/security_report.rs
This prevents projects expanding Subresource Integrity coverage from ingesting, grouping, and surfacing policy violations in Sentry.
via ADV.
--
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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