ShipCheck keeps getting better.

New ways to catch regressions, understand behavior changes, protect important code paths, and verify pull requests before they ship.

September 1, 2026Behavior history

Behavior History

ShipCheck can now remember how protected repository behavior evolves over time and trace where that behavior originally came from.

Behavior lifecycle tracking

Protected behaviors can record when they were introduced, preserved, violated, restored, or intentionally changed.

Git history origin tracing

ShipCheck can inspect repository history to find the earliest supported commit where a protected behavior became true.

Cross-file evidence

Origin analysis can follow related implementation files, helpers, authorization logic, validation, and tests instead of relying only on the file where the Behavior Guard was discovered.

Origin evidence

Historical introductions include the source commit, strongest supporting file, confidence score, and an explanation of why that commit established the behavior.

Intentional vs accidental changes

Developer-confirmed behavior changes can be distinguished from regressions, creating a more accurate record of what the repository is expected to do.

August 30, 2026Reliability

More reliable scans

ShipCheck's scan infrastructure became more resilient for real-world repository workloads.

Safer background processing

Improved scan queue and worker behavior so interrupted scans can recover more reliably.

Retry handling

Failed or interrupted scan jobs can be retried instead of becoming permanently stuck.

Stale job recovery

ShipCheck can detect abandoned scan work and recover it without requiring manual intervention.

August 24, 2026Behavior Guard

Behavior Guard

Repositories can preserve important behavioral expectations and make them part of future pull request review.

Protected behavior

Protect repository behaviors and safeguards that future pull requests should preserve.

Behavior-aware review

Pull requests can be evaluated against previously protected behavior instead of being reviewed only as isolated code changes.

Stronger regression detection

Behavior Guard gives ShipCheck additional context for recognizing when a reasonable-looking change weakens behavior the repository depends on.

August 20, 2026Testing

Regression tests from findings

ShipCheck can turn behavioral findings into regression tests that preserve the behavior developers actually care about.

Generate Regression Test

Generate a test directly from a ShipCheck finding to capture the behavior that should continue working.

Behavior-focused tests

Generated tests target the behavioral regression identified by ShipCheck instead of producing generic test coverage.

Better prevention

Once a regression is fixed, its expected behavior can be encoded in the test suite so the same class of issue is less likely to return.

August 20, 2026GitHub

GitHub-native workflow

ShipCheck became increasingly centered around the pull request workflow developers already use.

GitHub App installation

Connect ShipCheck through the GitHub App and choose which repositories it can access.

Pull request scanning

Review connected repositories and their pull requests directly through ShipCheck.

No personal access token required

Repository access is handled through the GitHub App installation flow instead of requiring personal access tokens.

August 17, 2026Repository controls

Per-repository settings

Different codebases need different review behavior, so ShipCheck added repository-specific controls.

AI review controls

AI-enhanced behavioral analysis can be controlled independently for individual repositories.

Category controls

Security, Reliability, Code Quality, Accessibility, and Testing analysis can be enabled or disabled independently.

Ignored paths and rules

Exclude generated files, documentation, vendored code, snapshots, and rules that do not apply to a repository.

August 15, 2026Safe fixes

Safer Apply Fix

ShipCheck's automated fixes became more careful about the exact pull request revision they modify.

Revision-aware fixes

Before applying a fix, ShipCheck verifies that the pull request has not changed since the finding was produced.

Atomic edits

Related file changes are applied together so fixes do not leave the repository in a partially updated state.

Automatic stale detection

After code changes, previous scan results are marked stale so developers know the pull request should be verified again.

August 14, 2026Scan history

Track findings across revisions

ShipCheck began tracking how findings change while a pull request evolves.

New findings

See which issues were introduced by the latest pull request revision.

Still present

See which previously detected findings remain unresolved.

Resolved

See which findings disappeared after the pull request was updated.

Reopened

Recognize when a previously resolved finding appears again later.

Scan-to-scan changes

Revision metadata, verdicts, Ship Score changes, and scan deltas make it easier to understand what changed between runs.

August 12, 2026Product

Ship Score and risk categories

Scan results became easier to prioritize with a single risk score and clearer finding categories.

Ship Score

Pull requests receive a score that summarizes the level of risk ShipCheck identified.

Ship verdict

Scans surface a clear recommendation about whether a pull request appears safe to ship or needs review first.

Five review categories

Findings are organized into Security, Reliability, Code Quality, Accessibility, and Testing.

Severity prioritization

Critical findings, warnings, and informational findings make it easier to focus on the changes that matter most.

August 11, 2026Core

Behavioral regression review

ShipCheck's core review model shifted from identifying questionable code to understanding how a pull request changes existing behavior.

Before and after behavior

Findings explain what behavior existed before the pull request and what behavior exists after it.

Removed safeguards

ShipCheck looks for validation, authorization, normalization, error handling, and other protections that became weaker or disappeared.

Broken contracts

Changes to APIs, callers, state transitions, assumptions, and repository conventions can be identified as behavioral risk.

Repository context

Analysis uses relevant code outside the changed lines to understand the contracts and assumptions surrounding a pull request.

Testing gaps

Behavior changes that should be protected by regression tests are surfaced during review.

August 2026Launch

ShipCheck beta

ShipCheck opened its beta for developers who want an additional verification layer before merging AI-generated and human-written code.

Pull request scanning

Connect a repository and analyze pull requests for behavioral regressions and risky changes.

Built for AI-assisted development

ShipCheck is designed for a world where tools like Cursor, Claude Code, Codex, and Copilot can produce large amounts of plausible-looking code quickly.

Pre-ship verification

Catch unintended behavior changes before they reach production.