The Ovvoc dashboard gives you full visibility into every repository, job, pull request, and billing event. This guide walks through each section.

Overview page

The dashboard home shows summary cards with your current status at a glance:

Active repositories: Count of monitored repos
Pending updates: Queued dependency updates
Open PRs: Pull requests waiting for review
Success rate: Percentage of updates that passed all stages

Repositories

The repository list shows each connected repo with a status indicator:

Monitoring — actively watching for new versions
Scanning — initial dependency scan in progress
Updating — a job is currently running
Idle — all dependencies are up to date

Repository detail

Click any repo to see its dependency overview: total dependencies, outdated count, recent jobs, and open PRs. The dependency list shows each package with its current and latest version.

Repository settings

Each repository has configurable settings:

Update schedule: Frequency of update checks (hourly, daily, weekly)
Branch strategy: Target branch for PRs
Dependency filtering: Include/exclude specific packages
Priority: Processing order relative to other repos

Updates

The updates page lists all detected dependency updates across your repositories. Filter by status (pending, in-progress, completed, failed), repository, or severity level.

Jobs

Every pipeline execution is a job. The jobs list shows each run with its status, repository, dependency, and timing.

Job detail

Click a job to see the full 10-stage breakdown. Each stage shows pass/fail status, timing, and any output. For failed jobs, you'll see the structured failure report:

Failure report

Job #1847 — express 4.21.0 → 5.2.1
Status: FAILED at Stage 9 (Test)

Transforms applied:
  ✓ function_rename: app.del() → app.delete()
  ✓ syntax_change: wildcard * → {*path}
  ✓ syntax_change: optional :param? → {/:param}

Test output:
  FAIL tests/routes.test.js
    ✕ GET /users/:id should return user (12ms)
      Expected: 200
      Received: 404

  23/24 tests passed, 1 failed

Suggestion: The route pattern change may require
updating test fixtures that use path matching.

Pull Requests

View all PRs created by Ovvoc across your repositories. Each entry shows:

PR status: open, merged, or closed
Confidence score (0.0–1.0)
Direct link to the PR on GitHub
The dependency and version range

Billing

The billing page shows your current plan, usage for the billing period, repository count, and invoice history. See the Pricing page for plan details.

Failure reports

Every failed job generates a structured failure report accessible from the job detail page. Reports include:

Report structure

{
  "job_id": 1847,
  "stage": "test",
  "dependency": "express",
  "from_version": "4.21.0",
  "to_version": "5.2.1",
  "transforms_applied": [...],
  "error": {
    "type": "test_failure",
    "output": "...",
    "failed_tests": ["tests/routes.test.js"]
  },
  "suggestion": "Review route pattern changes...",
  "timestamp": "2026-02-10T14:30:00Z"
}

Failure reports are retained for 30 days and can be exported as JSON.

Page-by-page walkthrough

The Ovvoc dashboard consists of eight distinct pages, each focused on a specific aspect of your dependency management workflow. Here is what you will find on each page:

Dashboard (overview): The landing page after sign-in. Shows summary statistics including active repository count, pending updates, open PRs, and overall success rate. Below the stats, a list of recent jobs and any active failures that need attention. This is your daily starting point.
Repositories: Lists every connected repository with its monitoring status (monitoring, scanning, updating, or idle), total dependency count, outdated dependency count, and the timestamp of the last scan. Click any row to navigate to the repository detail page.
Repository Detail: Shows the full dependency table for a single repo. Each dependency is listed with its current version, latest available version, dependency type (production, dev, peer), and update status. The page also shows recent jobs and open PRs for that specific repository.
Updates: A global view of all detected version changes across every repository. Each update shows the package name, current and target version, assigned category, severity level (critical, high, medium, low), and processing status. Updates are sorted by priority with security advisories at the top.
Jobs: Lists every pipeline execution with the update type (version-only, AST transform, AI-assisted), strategy used, current status, and total duration. This page provides a chronological view of all work Ovvoc has done across your repositories.
Job Detail: The most detailed view in the dashboard. Shows the full 10-stage pipeline result for a single job, including pass/fail status for each stage, build output, test results, AI token usage (only non-zero for categories 14+), the failure report (if applicable), and a link to the created PR.
Pull Requests: Lists all PRs created by Ovvoc with their current status (open, merged, closed), confidence score, the dependency and version range, and a direct link to the PR on GitHub. Filter by status to see which PRs still need your review.
Billing: Shows your current plan, the number of repositories in this billing period, total jobs run, cost breakdown by update type, and a full invoice history. See the Pricing page for plan details.

Reading job results

Every job in the dashboard has a status that tells you exactly where it is in the pipeline:

Pending: The job has been queued but not yet picked up by a worker. This is normal during high-volume periods.
Claimed: A worker has picked up the job and is preparing the container. This usually lasts only a few seconds.
Running: The job is actively executing the pipeline stages. You can check back to see which stage it is currently on.
Succeeded: All 10 stages passed and a pull request has been created. Click the PR link to review and merge.
Failed: The pipeline stopped at a specific stage and generated a failure report. Click into the job detail to see what went wrong.

The duration field shows the total pipeline time from container creation to PR creation (or failure). Typical values range from 30 seconds for version-only updates to 5 minutes for AI-assisted migrations.

The AI tokens field is only non-zero for updates in categories 14–25 that required AI assistance. It shows how many tokens were consumed for code generation and validation. This contributes to your billing usage.

The confidence score ranges from 0.0 to 1.0. A score of 1.0 means every applied transform was fully deterministic with no ambiguity. Scores below 1.0 indicate that some transforms involved AI assistance or edge-case heuristics — review these PRs more carefully.

Understanding failure reports

When a job fails, the failure report provides structured information to help you understand what happened and what to do next. Failures are categorized by the stage where they occurred:

Build failures: The project failed to compile after the update. The report includes the full compilation error output, the exit code, the exact build command that was run (npm run build), and a list of all files that were modified by transforms. Common causes include type mismatches from updated @types packages, missing exports in the new version, or breaking API changes not covered by existing rules.
Test failures: One or more tests failed after the update. The report includes the names of failed tests, their error messages, the total test count (passed/failed/skipped), and a baseline comparison. The baseline shows whether these same tests were already failing before the update — pre-existing failures are excluded from the pass/fail determination.
Transform failures: A code transformation rule could not be applied. The report lists which rules were attempted, which files they targeted, and the specific error (AST parse failure, pattern not found in source, conflicting transforms). Partial transforms that succeeded before the failure are also listed.
Install failures: npm install failed, typically due to peer dependency conflicts, a yanked package version, or npm registry issues. The report includes the npm error output and the exact dependency resolution conflict.

Each failure report includes a suggested actions section with specific recommendations. For example, a build failure might suggest “Check type annotations in src/api/handler.ts where express.Request.params was changed from string to string | string[]”.

Filtering and searching

All list pages in the dashboard support filtering and sorting to help you find what you are looking for quickly:

Filter jobs by status: Use the status dropdown to show only pending, running, succeeded, or failed jobs. This is useful for finding jobs that need attention.
Filter updates by severity: Focus on critical and high-severity updates first. Security advisories are always marked as critical or high.
Filter repos by monitoring status: Quickly find repos that are actively updating, idle, or in the middle of a scan.
Sort by date, priority, or duration: Click any column header to sort ascending or descending. Default sort is by date (newest first) for jobs and updates, and by name for repositories.

All tables support column sorting by clicking the column header. Click once for ascending, click again for descending. The current sort column and direction are indicated by an arrow icon in the header.

Dashboard Guide