sourcefuse/arc-docs

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.

6 of your 8 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 278.1s for a 220.0 MB repo slow.
Repobility's analysis ran in 0.91s after the clone landed.

https://github.com/sourcefuse/arc-docs · scanned 2026-06-05 13:33 UTC (5 days, 7 hours ago) · 10 languages

7 findings 11/13 scanners ran 91st percentile · Unknown ·

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

3 actionable findings from 1 signal source. 4 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	50.0	0.15	7.50
`security_score`	100.0	0.25	25.00
`testing_score`	70.0	0.20	14.00
`documentation_score`	40.0	0.15	6.00
`practices_score`	90.0	0.15	13.50
`code_quality`	80.0	0.10	8.00
Overall		1.00	74.0

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 0 Low 2 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 3 System graph 0 Crowd 0 Layer: Quality 1 Cicd 1 Software 1

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Config drift 1 finding

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

1 matching finding on this repo

high [MINED131] pre-commit hook `https://github.com/pre-commit/pre-commit-hooks` pin… .pre-commit-config.yaml:4

View all config drift findings →

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/2604dad1-9bc4-467f-84a8-e82cfcd7ecbc/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2604dad1-9bc4-467f-84a8-e82cfcd7ecbc/

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.