https://github.com/tmadzik/victus-ai
· scanned 2026-06-16 04:40 UTC (1 month, 3 weeks ago)
2 raw signals (0 security + 2 graph)
Last scanned 1 month, 3 weeks ago · v1 · 2 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.
All 16 nodes from the latest scan, grouped by kind. Each node is a unit the engine identified (file, function, endpoint, table…). Most users won't need this view — it's primarily for debugging the engine's graph extraction or for AI agents that want to enumerate the project structure.
| Label | Layer | Status | Path |
|---|---|---|---|
.env.example |
software | healthy | .env.example |
pnpm-workspace.yaml |
software | healthy | pnpm-workspace.yaml |
.prettierrc.json |
software | healthy | .prettierrc.json |
tsconfig.base.json |
software | healthy | tsconfig.base.json |
README.md |
software | healthy | README.md |
package.json |
software | healthy | package.json |
turbo.json |
software | healthy | turbo.json |
pnpm-lock.yaml |
software | healthy | pnpm-lock.yaml |
| Label | Layer | Status | Path |
|---|---|---|---|
postgres |
data | healthy | .env.example |
postgresql |
data | healthy | .env.example |
| Label | Layer | Status | Path |
|---|---|---|---|
port:64 |
network | healthy | pnpm-lock.yaml |
port:15 |
network | healthy | pnpm-lock.yaml |
| Label | Layer | Status | Path |
|---|---|---|---|
vps::aws |
hardware | healthy | .env.example |
vps::gcp |
hardware | healthy | .env.example |
| Label | Layer | Status | Path |
|---|---|---|---|
tmadzik__victus-ai |
software | healthy | /data/fable5_failed_archive/tmadzik__victus-ai |
| Label | Layer | Status | Path |
|---|---|---|---|
auth::README.md |
security | healthy | README.md |
This page is publicly accessible at:
https://repobility.com/scan/c77450e3-4f2a-46d1-b697-b0b49a0c7198/
To check status programmatically (no auth required):
curl -s https://repobility.com/api/v1/public/scan/c77450e3-4f2a-46d1-b697-b0b49a0c7198/
Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.