Enji GuardSafety and access
Provider and write matrix
Compare repository reads, provider artifacts, active website requests, and the human approval boundary.
Capability summary
This matrix summarizes current published workflow boundaries. Exact behavior still depends on repository access, provider capability, the selected write mode, and the individual runbook’s safety gates.
| Capability | GitHub | GitLab | External side effect | Human boundary |
|---|---|---|---|---|
| Repository connection | GitHub App | Token and configured host | Connection state | User selects access |
| Read-only audits | Supported | Provider-aware execution | None in repository | User starts or schedules |
| Code review | Pull request comment | Merge request note | Review response | Review cannot mutate code |
| Vulnerability autofix | Issue and optional pull request | Issue and optional merge request | Provider artifacts | Guard never merges |
| Dependency update | Bounded review request when verified | Provider-aware review request | Provider artifacts | One root cause per run |
| Test writing | Review request when verified | Provider-aware review request | Provider artifacts | Tests and test helpers only |
| Auto-pentest | Exact linked website | Exact linked website | Active website requests | Explicit authorization and consent |
| Repository summary | Private or public link | Private or public link | Optional public report | Owner can make private, revoke, or delete |
Read-only does not mean zero access
An audit still needs repository data to collect evidence. Read-only means the workflow does not write repository files or provider artifacts.
Write-capable does not mean autonomous merge
Supported improvements may create issues, pull requests, merge requests, comments, or notes. A human remains responsible for reviewing and merging code changes.
Issue-plus-review-request mode is permission to attempt a safe proposal, not a guarantee that a run will write code. Duplicate work, stale evidence, high blast radius, and failed verification can preserve an issue-only or no-write outcome.
Provider exceptions
Provider-aware execution does not guarantee that every report link and summary source behaves identically across GitHub, GitLab Cloud, and self-hosted GitLab.
Read Connect GitHub or Connect GitLab for provider-specific setup.