Skip to main content
The Pull Requests page shows security scan results for GitHub PRs, helping you catch issues before code is merged.

Pull Request List

View all PRs with security scans:
ColumnDescription
PRPR number and title
RepositorySource repository
StatusScan status (Pending, Scanning, Complete, Failed)
IssuesNumber of security issues found
CreatedWhen the PR was opened

PR Detail View

Click a PR to see:
  • Security issues introduced in this PR
  • Code changes that triggered each finding
  • Link to GitHub for the full PR context
  • Scan history for the PR

PR-Specific Filtering

Issues shown are filtered to changes in the PR only. This helps you focus on new vulnerabilities rather than pre-existing issues.

Scan Triggers

PRs are automatically scanned when:
  1. PR Created - Initial scan on new PR
  2. PR Updated - Re-scan when new commits are pushed
  3. Manual Trigger - Click “Scan” on the PR
Auto-scan requires GitHub Integration to be configured.

PR Status Indicators

StatusMeaning
PendingScan queued
ScanningScan in progress
CompleteScan finished
FailedScan encountered an error

GitHub PR Comments

When scans complete, Vidoc posts findings as PR comments:
  • Inline comments on specific lines of code
  • Summary comment with all findings
See PR Comments to configure comment behavior.

Enabling PR Scans

To scan PRs automatically:
  1. Connect GitHub
  2. Enable auto-scan for the repository
  3. Create or update a PR