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.

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

Scan timing: clone 1.23s · analysis 7.12s · 0.1 MB · GitHub API rate-limit (preflight)

0913vision/church_media_server

https://github.com/0913vision/church_media_server · scanned 2026-06-16 03:37 UTC (2 months ago) · 10 languages

24 raw signals (14 security + 10 graph) 40th percentile · Typescript · small (2-20K LoC) System graph score 93 (lower by 21)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v1 · 23 actionable findings from 2 signal sources. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 10 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	75.0	0.15	11.25
`security_score`	86.8	0.25	21.70
`testing_score`	84.0	0.20	16.80
`documentation_score`	50.0	0.15	7.50
`practices_score`	42.0	0.15	6.30
`code_quality`	80.0	0.10	8.00
Overall		1.00	71.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 5 Medium 5 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 13 System graph 10 Crowd 0 Layer: Software 6 Quality 12 Frontend 2 Security 2 Cicd 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 2 findings

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.

2 matching findings on this repo

medium No CI/CD configuration found
medium Insecure pattern 'cors_wildcard' in server/constants/socketConfig.ts:19 server/constants/socketConfig.ts:19

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/d1c80b3d-aafd-45d4-b282-234503e65edd/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d1c80b3d-aafd-45d4-b282-234503e65edd/

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.