Enji GuardEnji Guard documentation
Move a project toward the green zone, keep it healthy with recurring audits, and review the focused improvements Guard prepares when risks return.
Connect your first repository
Check prerequisites, choose GitHub or GitLab, and understand what Guard can access.
Follow the product lifecycle
Start with the outcome, then move through setup, audits, and reviewable improvements.
Check access, provider, project, and automation choices before Guard reads repository data.
Read article Understand Guard The green zoneUnderstand the maintained project-health outcome that recurring audits and bounded improvements support.
Read article Audits Audits overviewUnderstand the read-only audit lifecycle, current revision boundary, evidence, scores, reruns, and history.
Read article Improvements Improvements overviewUnderstand how Guard turns current evidence into one bounded improvement at a time.
Read articleComplete documentation map
Browse the complete product lifecycle, from repository setup and audit evidence to improvements, automation, reports, safety, and troubleshooting.
Getting started
6Connect an account, repository, and optional website, then complete the first scan.
Start here
Repository providers
Project setup
Understand Guard
4Learn the green-zone model, project scope, evidence, and health loop.
Product model
Projects and scope
Health and evidence
Audits
13Run, schedule, and understand audits, then browse every supported health area.
Using audits
Audit catalog
Improvements
13Turn current audit evidence into bounded work that a human can review and merge.
Using improvements
Review and outcomes
Improvement catalog
Automation
4Control schedules, triggers, notifications, code review, and active website testing.
Schedules and triggers
Continuous workflows
Reports and sharing
5Read run results and history, build summaries, and control public views.
Report types
History and activity
Summaries and sharing
Safety and access
4Understand repository access, provider writes, human approval, and testing consent.
Repository access
Write boundaries
Active testing
Troubleshooting
6Resolve connection, execution, score, Autofix, and automation problems.