Skip to content
Pullminder Docs

Dashboard overview

The Pullminder dashboard at app.pullminder.com is the primary interface for monitoring pull request risk across your organization. Sign in with your GitHub account to access all features.

Overview page

Section titled “Overview page”

The landing page provides a high-level snapshot of your organization’s PR health. Eight stat cards are displayed at the top:

CardWhat it shows
Total PRsNumber of pull requests analyzed in the selected period
High risk countPRs with a risk score above your configured threshold
Avg risk scoreMean risk score across all analyzed PRs
Rule pass ratePercentage of rule evaluations that passed without findings
FindingsTotal number of findings surfaced across all PRs
Test gapsPRs where changed code lacks corresponding test coverage
Active rulesNumber of rule packs currently installed and enabled
Coverage deltaAverage change in code coverage introduced by recent PRs

Below the stat cards, the overview page shows a risk trend chart plotting daily average risk scores over time, and a high-risk PRs list highlighting the pull requests that need immediate attention.

PR list

Section titled “PR list”

The PR list page shows every analyzed pull request in your organization. Use the filter bar to narrow results:

  • Status — filter by open, merged, or closed
  • Risk level — filter by low, medium, high, or critical
  • Repository — filter by one or more repositories
  • Search — free-text search across PR titles and authors

Each row shows the PR title, repository, author, risk score, finding count, and current status. Click any row to open the PR detail view.

PR detail

Section titled “PR detail”

The PR detail page provides the full analysis breakdown for a single pull request.

Risk breakdown — A visual breakdown of how the overall risk score was calculated, showing the contribution of each analyzer category (security, complexity, test coverage, policy violations, and others).

Findings — Every finding surfaced by your installed rule packs, grouped by severity. Each finding includes the file path, line range, rule that triggered it, and a description of the issue.

Coverage — If coverage data is available, this section shows which changed files have test coverage and which do not. Coverage artifacts must be configured in your repository settings.

Reviewer brief — The same structured summary that Pullminder posts as a PR comment. It highlights what changed, what matters most, and where to focus the review.

Rules management

Section titled “Rules management”

The rules page lets you manage which rule packs Pullminder runs against your PRs.

Installed rules — Lists every rule pack currently active in your organization. For each pack you can:

  • Set the action to block, warn, or notify. Block prevents merging when a finding triggers. Warn posts a comment but does not block. Notify sends an alert without commenting on the PR.
  • Configure overrides per repository to change the action or disable the pack entirely for specific repos.
  • Uninstall the pack to stop running it.
  • Upgrade to the latest version when the registry has a newer release.

Available rules — Browse rule packs from the Pullminder registry (or your custom registry, if configured). Install any pack with a single click.

Rule packs come in two types: detection packs that identify code patterns (e.g., hardcoded secrets, SQL injection) and policy packs that enforce team standards (e.g., require tests for auth modules).

Analytics

Section titled “Analytics”

The analytics page provides deeper insight into trends and patterns across your organization.

  • Risk trends — Daily or weekly risk score trends over time, filterable by repository
  • Category breakdown — Distribution of findings by category (security, complexity, test gaps, policy)
  • Review time — How long PRs spend in review, correlated with risk score
  • Recurring patterns — Findings that appear repeatedly across PRs, suggesting systemic issues
  • Repository breakdown — Per-repo comparison of risk scores, finding counts, and review velocity
  • Reviewer activity — Review volume and response time per team member
  • Coverage trend — Code coverage changes over time across repositories

Alerts

Section titled “Alerts”

The alerts page lists notifications for events that require attention:

  • High-risk PRs — A PR exceeded the risk threshold configured for your organization
  • Policy blocks — A rule with the block action triggered, preventing a PR from merging

Alerts appear in the dashboard and can also be sent to Slack if you have configured webhook integration. Use the Mark read action to dismiss alerts you have reviewed.

Reports

Section titled “Reports”

The reports section provides organization-wide analysis.

Baseline analysis — Shows the results of a historical baseline scan. When you trigger a baseline scan from settings, Pullminder analyzes recent merged PRs to establish a risk profile for each repository. The report shows per-repo risk scores, common finding categories, and areas for improvement.

Next steps

Section titled “Next steps”