New to repository security?
Install Repyy, scan a local folder, and learn what the report can and cannot tell you.
Follow the first scan guide →Documentation
Start with a scan.Choose your boundary.
repyy reads repository files as data and gives you a review report. Start with the path that fits your task, then open a focused guide for flags, configuration, isolation, or coverage details.
Static reviewTarget code is not intentionally runLocalReports stay with youExplicitNetwork and updates are opt in
What repyy does not do
A normal scan does not intentionally install packages, build the target, run its tests, or execute its source. Host Git or Docker may run when you request those modes.
Choose your path
Know your way around the CLI?
Find the right flags, report format, and commands for repeatable reviews.
Open the CLI reference →Assess the tool itself?
Trace release evidence, test coverage, and the limits of the security boundary.
Read trust and limitations →Run your first scan
Install repyy on the computer where you will review the code. A local folder needs repyy only. Git is needed for a remote URL in host mode.
Install with Homebrew
brew install --cask Kevin-Umali/tap/repyyScan and save HTML
repyy scan ./repository --format html --output report.htmlOpen report.html directly from your file manager. It is self-contained and works as a local file:// page; a remote source link may open the provider website in your browser.
Copyable starting points
Replace the sample path or URL with a target you are allowed to inspect. Review the result before opening the repository in a trusted workspace.
Review downloaded code
No Git or network is needed.
repyy scan ./assignmentInspect before checkout
Host mode needs Git on PATH.
repyy scan https://github.com/org/repoSave structured output
JSON and SARIF fit existing review tools.
repyy scan ./repo --format sarif --output report.sarifUse Docker
Pull the signed, digest-pinned release image first.
repyy scan ./repo --sandbox=dockerRead the result
The verdict is a review decision aid, not a safety certificate. Check coverage before acting on any result.
No enabled rule matched within completed coverage.
Findings need a person to inspect their context.
High-confidence critical behavior needs a controlled decision before execution.
A timeout, limit, permission, clone, archive, or read error reduced coverage. Exit code is 2.
Choose a report
TerminalPrioritized human review
--format terminalJSONAutomation and saved input
--format jsonSARIFCode-scanning integrations
--format sarifHTMLPrivate offline review
--format htmlRender a saved JSON scan
repyy report report.scan.json --format html --output report.htmlHTML reports are rendered by the host, including after Docker scans. Keep report files private because paths and evidence can still reveal repository structure.
Compare output formats and flags →Know the boundary
Local scans need no network. Remote host scans fetch the URL you request with Git; Docker separates HTTPS fetching from analysis, which requests --network none. Intelligence updates happen only when you run the update command. Provider credentials stay in the process environment and out of URLs.
Review Docker's controls
Read isolation details →Use the opt-in Docker backend and review its limits in the isolation guide.
What “intel” means
Intel means threat intelligence: a dated, signed offline snapshot of sourced package/version advisories and exact file hashes. It is separate from repyy’s built-in behavioral rules, and a match is a reason to review rather than proof by itself.
Built-in rulesFind suspicious behavior and context in source, manifests, automation, and metadata.
Intel snapshotAdds sourced package/version and exact hash indicators.
Check the active snapshot
repyy intel statusGive your coding agent a safe first step
The optional repyy agent skill tells a coding agent to scan unfamiliar repositories before execution, keep source local, and treat incomplete coverage as unresolved. It installs instructions only; the repyy CLI is installed separately.
Install for Codex
npx skills add Kevin-Umali/repyy --skill repyy -g -a codex -yWhen coverage is incomplete
Resource limits protect the scanner from hostile repositories and archives. A timeout, unreadable file, denied mount, failed fetch, or exceeded limit is reported asSCAN INCOMPLETE; successful targets remain visible in a mixed scan.
Repository10 minute timeout · 100,000 files · 50 MiB per file
Archive10,000 entries · 1 GiB expanded bytes · 3 nested levels