https://github.com/val-town/val-town-docs
· scanned 2026-06-16 04:40 UTC (1 month, 2 weeks ago)
5 raw signals (0 security + 5 graph)
Last scanned 1 month, 2 weeks ago · v1 · 5 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.
All 18 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 |
|---|---|---|---|
ec.config.mjs |
software | healthy | ec.config.mjs |
renovate.json |
software | healthy | renovate.json |
CLAUDE.md |
software | healthy | CLAUDE.md |
mise.toml |
software | healthy | mise.toml |
package-lock.json |
software | healthy | package-lock.json |
README.md |
software | healthy | README.md |
astro.config.mjs |
software | healthy | astro.config.mjs |
lychee.toml |
software | healthy | lychee.toml |
package.json |
software | healthy | package.json |
cspell.json |
software | healthy | cspell.json |
biome.json |
software | healthy | biome.json |
tsconfig.json |
software | healthy | tsconfig.json |
CLAUDE.md |
quality | healthy | CLAUDE.md |
| Label | Layer | Status | Path |
|---|---|---|---|
redis |
data | healthy | package-lock.json |
sqlite |
data | healthy | astro.config.mjs |
| Label | Layer | Status | Path |
|---|---|---|---|
vps::aws |
hardware | healthy | package-lock.json |
vps::azure |
hardware | healthy | package-lock.json |
| Label | Layer | Status | Path |
|---|---|---|---|
val-town__val-town-docs |
software | healthy | /data/fable5_failed_archive/val-town__val-town-docs |
This page is publicly accessible at:
https://repobility.com/scan/55e2f75e-f403-4c60-8dc1-5f38921b1351/
To check status programmatically (no auth required):
curl -s https://repobility.com/api/v1/public/scan/55e2f75e-f403-4c60-8dc1-5f38921b1351/
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.