Everything Enji Guard checks, in one place

Check for common security problems and unsafe patterns.

Test one verified, consented website with non-destructive requests, confirm findings from reproducible proof, and score the live site.

Check whether the repository is easy for agents to understand and change.

Measure coverage, flaky tests and recent testing activity.

Check whether automated delivery protects the default branch and releases, and identify the sequence of steps to make the pipeline reliable.

Find repository clutter, dead code, hardcoded values, weak maintenance commands, and patterns that make future changes harder.

Check whether project configuration is manageable, practical, clean, and understandable, and identify the next steps to reduce setup effort and improve maintainability.

Check whether repository dependencies are accumulating risk or disorder that makes safe development harder, using scanner-backed evidence and key verification gaps.

Check whether the repository shows what the system is for, why key decisions were made, and how its behavior is verified, without guessing.

Find disconnected code, configuration, flags, metadata, and dependency anchors that make current repository behavior harder to understand.

Check whether the repository is ready to become or remain a credible open source project.

The autofix jobs that turn audit findings into reviewable work.

See the format before you connect a repo.