Skip to content
By JTT
Menu

VibeCheck · Tools

What did the AI leave behind?

Paste a public GitHub repository. VibeCheck runs six bounded source-quality checks and returns a single Source Score with the evidence behind it.

Get your Source ScoreInstall the CLI (opens in a new tab)

01 / What it checks

Six checks. Evidence-based findings.

  • Accessibility

    Missing image alternatives, unlabeled inputs, language declarations, and viewport basics in supported source files.

  • Performance

    Large image files and potentially render-blocking stylesheet patterns visible in the repository.

  • Security patterns

    Risky source patterns such as eval, dynamic HTML, mixed-content links, missing CSP signals, and potential hardcoded secrets.

  • Duplication

    Identical source files that add maintenance cost or make a project harder to understand.

  • Tests

    Whether supported test files are present. A signal of coverage, not proof that tests are sufficient or passing.

  • Documentation

    Whether the repository includes a README that helps people and tools understand the project.

02 / The score

A Source Score. Not a wall of noise.

Weighted by severity: high-severity findings reduce the score more than medium- and low-severity findings. It summarises only the checks VibeCheck performs, and it is a review aid, not a substitute for testing the deployed product.

  1. A
    90+

    Strong signals across the checks.

  2. B
    75–89

    Small gaps worth a look.

  3. C
    50–74

    Significant gaps to plan around.

  4. D/F
    Under 50

    Major gaps. Prioritise the findings.

03 / How it works

Three steps. No accounts. No dashboards.

  1. 01

    Paste a public repository URL

    The browser experience analyses supported repository files through the VibeCheck engine and returns a source-quality report.

  2. 02

    Six checks run against the source

    Accessibility, performance, security patterns, duplication, tests, and documentation, from the files VibeCheck can analyse.

  3. 03

    Review the score and its findings

    Every finding carries confidence and a practical next step, with uncertainty called out where the heuristic may be wrong.

04 / Philosophy

A smaller tool with visible limits beats a bigger tool with vague promises.
  • Keep the scope of its checks visible
  • Show confidence and a practical fix with each finding
  • Summarise supported checks without claiming full release readiness
  • Improve from feedback rather than assumed needs

See what your source reveals.

No account or dashboard. Paste a public GitHub URL, inspect the bounded result, then decide what needs deeper review.

Get your Source Score