Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

rifted-game/content

https://github.com/rifted-game/content · scanned 2026-06-16 04:37 UTC (1 month, 3 weeks ago)

3 raw signals (0 security + 3 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 3 weeks ago · v1 · 3 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

All 9 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.

LabelLayerStatusPath
lint-staged.config.ts software healthy lint-staged.config.ts
tsconfig.base.json software healthy tsconfig.base.json
README.md software healthy README.md
LICENSE software healthy LICENSE
lefthook.yml software healthy lefthook.yml
package.json software healthy package.json
biome.json software healthy biome.json
bun.lock software healthy bun.lock

LabelLayerStatusPath
rifted-game__content software healthy /data/fable5_failed_archive/rifted-game__content
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/8b6a433c-bab7-46f3-a60e-01f6de4f063f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8b6a433c-bab7-46f3-a60e-01f6de4f063f/

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.