Infiniview docs
Launch scans, connect GitHub, configure scanners, review forensic findings, and export proof.
What is Infiniview
Infiniview is a security review platform that takes a repository, builds and runs it in a sandbox, and combines static analysis, dependency audits, secret detection, IaC scanning, and runtime agents into one stream of evidence. Each scan persists severity, fingerprints, locations, replay artifacts, delta state, and suppression memory so you can decide what to fix without re-deriving context.
You operate the product through the dashboard or directly from GitHub pull requests. Settings can live in the dashboard, the repo’s .infiniview.yml, or both — repo config wins for overlapping fields, and every scan freezes the merged settings into a snapshot so changing settings mid-run never affects the active scan.
How the docs are organized
- Get started walks first-time operators from sign-in to a proof bundle.
- Operate covers the scan lifecycle, GitHub automation rules, and the configuration model.
- Tooling lists the available scanners and runtime agents.
- Findings & proof explains evidence shape, trust scoring, readiness, and exports.
- Reference contains the dashboard API contract and the operator FAQ.
Product surfaces
The dashboard is split into a small number of named surfaces. Most operator tasks happen in one of these — the rest of the docs assume you’ve seen them.
Default dashboard view for recent reviews, selected review detail, story insights, readiness, and reruns.
Backlog across reviews with severity, source, exploitability, delta, category, suppression, and search filters.
Scanner, runtime-agent, threshold, exclude-list, timeout, max-plan, and evidence-detail configuration.
GitHub auto-review repos, own-PR filtering, push debounce, encrypted repo secrets, and completion emails.
Run timeline with phase durations, scanner coverage, compare counts, trust score, gaps, and recommendations.
Cmd+K navigation across reviews, findings, settings, security configuration, scan history, and finding detail.
What to read next
- Quickstartif you haven’t connected GitHub or run your first scan yet.
- Scan workflow for the trigger-to-proof lifecycle and what the snapshot freezes.
- GitHub automation for PR triggers, debounce, and trusted bot commands.
- API referenceif you’re scripting around the dashboard.