How caidensilverstein-svg/corvus works
Corvus detects the host platform, selects compatible tools from its static matrix, then previews or installs them through the native package manager and reports the outcome. The CLI also supports listing, category/tool filtering, dry runs, matrix-hash verification, and optional package-index synchronization. The graph follows the sampled Python call sites; package-manager execution is an external boundary. The matrix and report files are shown as persisted data. Installation internals are summarized at the installer component rather than split into unsampled helpers.
Main entry points: cli.py CLI orchestration · installer.py Install and conflicts · main.py Python entry point · matrix.py Tool matrix
Components 11
User workflow
- Python entry point
main.py - CLI orchestration
corvus/cli.py
Platform and catalog
- Platform detection
corvus/detect.py - Tool matrix
corvus/matrix.py - Tool definitions
data/tools.json
Installation
- Install and conflicts
corvus/installer.py - Native package manager
- Rollback log
corvus/installer.py
Reporting
- Report generator
corvus/report.py - Last-run report
corvus/report.py
Other components
- Operator
Connections 11
- Operator → Python entry point: runs
README.md - Python entry point → CLI orchestration: calls
main.py - CLI orchestration → Platform detection: detects host
corvus/cli.py - CLI orchestration → Tool matrix: selects tools
corvus/cli.py - Tool matrix → Tool definitions: loads
corvus/matrix.py - CLI orchestration → Tool definitions: hashes
corvus/cli.py - CLI orchestration → Install and conflicts: runs install
corvus/cli.py - Install and conflicts → Native package manager: executes commands
corvus/installer.py - Install and conflicts → Rollback log: appends entries
corvus/installer.py - CLI orchestration → Report generator: generates report
corvus/cli.py - Report generator → Last-run report: writes report
corvus/report.py