airom repo <url|path> scans a git repository. The target is interpreted by what it is:
Local worktree
Remote URL
./foo exists on disk, it is scanned as a worktree even if a remote of the same name exists. Anything that is neither an existing path nor a recognized remote URL is a usage error.
airom scan <target> reaches repo automatically when the target is not an existing local path but does look like a git URL. Use the repo: prefix to force it.Recognized remote URLs
https://, http://, ssh://, git://, and scp-like git@host:path.
Remote clones need git on PATH
Remote URLs are cloned by invoking thegit binary. There is no in-process clone fallback: if no git is on PATH, AIROM fails with a clear error rather than silently doing something else.
What AIROM runs
Git provenance
The repo source captures provenance for the worktree it scans, best-effort:
When a
git binary is present it is authoritative. When it is not, HEAD and the origin URL are still recovered by reading .git/HEAD, its target ref (loose or packed), and .git/config directly. Every step is best-effort: pointing repo at a directory that is not a git worktree yields empty provenance and the scan proceeds normally.
The resolved commit becomes the scan’s content identity (git:<commit>), falling back to the target string when no commit can be resolved.
Everything from fs applies
A repo scan is a directory scan of the worktree. Ignore handling (.gitignore + .airomignore stacks, non-overridable default skips, --ignore globs), --max-file-size, --io-budget, --parallel, and --select all behave exactly as documented in /scanning/filesystem.
Repo scan with the usual knobs
.git/ itself is a non-overridable default skip, so repository internals are never walked as scan content.
Working without a network
To scan a repository with no network access, clone it yourself and pointrepo at the local worktree — a local path is never fetched over the network.
No network: local worktree only