Team coverage
Which repositories have at least one team-based permission path?
Free GitHub Access Audit
Find GitHub repo access drift before signup
repod's free GitHub access audit gives private engineering orgs a fast first pass on repo access drift: direct grants, private repos without team coverage, high-privilege teams, and unclear ownership.
- No write access
- Read-oriented audit mode
- Before signup
- Preview the risk signals first
- 24 hours
- Unclaimed audit sessions expire
What it answers
Which access decisions need attention first?
The audit identifies repositories outside the team model, durable access held as individual exceptions, and teams with elevated permissions. It gives a platform lead a concrete starting queue rather than another inventory export.
For the complete operating workflow, see how the GitHub access audit tool moves from evidence to reviewed changes.
Signals
Four checks with a clear review decision
Each signal corresponds to a permission or ownership decision that can be verified in GitHub.
Private unassigned repos
Which private repositories have no team grant or clear owning group?
Direct staff mappings
Which user-to-repository grants sit outside the normal GitHub Team model?
High-privilege teams
Which teams hold Maintain or Admin and need an explicit justification?
Interpret the results with the GitHub Teams hierarchy and repository permissions guide and the explanation of GitHub Direct access vs Organization access.
Synthetic example
A report that turns drift into a review queue
These sample figures illustrate the report structure. A live audit calculates them from the selected GitHub organization.
Team coverage
Review repositories outside the team model first.
Private unassigned repos
Assign an owning team or document the exception.
Direct staff mappings
Move durable access into teams where practical.
High-privilege teams
Confirm that Maintain or Admin is still justified.
Manual worksheet
Run the same decisions in a spreadsheet
Use the template for a small review or to agree the fields your team needs before automating the process.
| Repository | Visibility | Owning team | Direct access | Review decision |
|---|---|---|---|---|
acme-platform/deployment-controller | Private | platform-engineering | alice-dev, vendor-reviewer | Replace durable direct access with team access; verify the vendor exception. |
The download also includes exception owner, expiry, permission, and notes columns. For a full manual process, use the GitHub repository permissions audit checklist or the GitHub repo access audit guide.