Inspect GauntletCI on real scenario pull requests
The demo repo contains 36 public scenario PRs. Each PR explains the intended behavior change, shows the code diff, and runs GitHub Actions checks you can inspect directly.
EricCogen/GauntletCI-Demo
Public repository · default branch main
36
open scenario PRs
C#
demo codebase
Actions
checks to inspect
$ git clone https://github.com/EricCogen/GauntletCI-Demo
$ gh pr list --repo EricCogen/GauntletCI-Demo
Curated starting points
Start with these PRs
These links go to GitHub so you can inspect the PR text, changed files, checks, and annotations in the same interface your team already uses.
Safe typo / wording fix
A one-line wording change that should not produce behavioral findings. Use it to judge whether the tool stays quiet on safe diffs.
Singleton captures scoped dependency
A singleton service captures scoped user context, creating a data-isolation and lifetime risk that is easy to miss in review.
Cache lookup removed
A cache read is removed during a simplification, shifting hot-path traffic directly to the database.
Blocking on async task
A request path blocks on async work, turning an implementation shortcut into a potential deadlock or thread-pool starvation risk.
Role-based authorization bypass
An authorization check moves inside conditional logic, changing who can reach a protected code path.
Breaking public package contract
A public API contract changes without the kind of compatibility signal library consumers need before merge.
Use it as a buyer proof point
Send reviewers directly to scenario PRs instead of asking them to trust a screenshot or marketing claim.
Compare clean vs risky diffs
Start with PR #277 as the clean control, then compare it with risk scenarios across security, async, API, and data behavior.
Inspect checks where they run
The demo stays on GitHub. You can inspect changed files, PR explanations, Actions runs, and check details without a custom sandbox.
Learn what the checks mean
Connect each demo finding back to the rule library
After you inspect a scenario PR, use the docs to understand the rule category, severity, and CI integration path behind the finding.