Skip to main content
Forge scans authorized GitHub repositories for concrete evidence of AI applications and their dependencies. Repository evidence is joined with endpoint, gateway, cloud, and identity signals to connect deployed activity to the code that defines it. The GitHub connection can also contribute provider-native non-human identities and ownership evidence. Agent access uses a separate provider authority so inventory collection does not silently grant Forge permission to change GitHub access.

​
Coverage

​
Detection

Each observation includes the repository, revision, file path, line number, content fingerprint, evidence quality, and confidence. Credential names may be identified; secret values are not collected.

​
Scan contract

Files with package manifests, AI/provider names, environment references, and application source paths are prioritized before lower-signal files.

​
Connection

​
Setup

  1. Open Integrations → GitHub and install the Forge GitHub App on the intended organization or user. Select only the repositories Forge should scan. A fine-grained token is also supported.
  2. Save the owner and an optional repository allowlist. An empty allowlist uses the repositories visible to the installation or token, subject to the per-run limit.
  3. Run a sync. Forge reports observationCount, canonicalInventoryCount, and blockers independently for each repository.
The GitHub App path records the installation ID, account login, account type, and GitHub repository-selection mode. App credentials are exchanged for short-lived installation access rather than stored as a user token.

​
Evidence

Repository evidence does not prove live usage, prompt or response content, tool execution, account identity, or policy enforcement. Connect a runtime integration to establish those facts.

​
Non-human identities and Agent access

When the connected GitHub scope and permissions provide the evidence, Forge adds GitHub machine principals and credentials to Identities → NHIs. Review their repository or organization scope, status, activity, credential posture, and available ownership evidence alongside NHIs from cloud providers. Agent identities can receive bounded GitHub access through provider-specific access limits, profiles, revisions, and assignments. This configuration is separate from repository scanning:
  • The inventory connection discovers repositories, artifacts, and available identity evidence.
  • The Agent access connection authorizes the exact GitHub operations Forge can issue for an assigned Agent identity.
  • Forge activates access only after the saved boundary and provider readback agree.
Use Non-human identities to investigate existing GitHub machine access and Agent identities to configure an autonomous workload’s governed access.

​
Permission troubleshooting

Validate with an installation token or fine-grained token whose owner and repository selection match the Forge connection. Do not paste the token into a command line; provide it through GH_TOKEN in your secret-managed shell.
A 404 can mean the repository is outside the installation selection, not that it does not exist. A 403 response includes the missing permission or policy restriction when GitHub exposes it. After changing an App permission, approve the updated installation permissions and run Forge Sync again.