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.

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

Scan timing: clone 13.72s · analysis 9.04s · 235.8 MB · GitHub API rate-limit (preflight)

Draigus/NBIAI-TEAM

https://github.com/Draigus/NBIAI-TEAM · scanned 2026-06-16 04:21 UTC (2 months ago) · 10 languages

136 raw signals (132 security + 4 graph) 11/13 scanners ran 22nd percentile · Javascript · large (100-500K LoC) System graph score 82 (lower by 19)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

55.6% cov · 4 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	100.0	0.25	25.00
`testing_score`	68.0	0.20	13.60
`documentation_score`	56.0	0.15	8.40
`practices_score`	40.0	0.15	6.00
`code_quality`	46.0	0.10	4.60
Overall		1.00	63.6

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 2 High 38 Medium 6 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 83 System graph 4 Crowd 0 Layer: Quality 68 Security 9 Cicd 3 Software 7

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.

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Archive or legacy directory is mixed into the active repository root _archive:1

View all legacy markers findings →

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

medium No CI/CD configuration found

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/b4c7e08e-a031-4687-978b-7c5a2cef4cef/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b4c7e08e-a031-4687-978b-7c5a2cef4cef/

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.