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.
Sign up free Scan another repo
22 of your 226 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.27s · analysis 82.08s · 5.4 MB · GitHub API rate-limit (preflight)

nestjs/nest

https://github.com/nestjs/nest · scanned 2026-06-05 07:44 UTC (5 days, 22 hours ago) · 10 languages

575 raw signals (203 security + 372 graph) 5th percentile · Typescript · large (100-500K LoC) System graph score 54 (higher by 2)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 22 hours ago · v2 · 270 actionable findings from 2 signal sources. 119 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
47.1
/100
Security checks
41
89 findings
System graph
54
100.0% cov · 181 findings
Critical
6
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 5.5 0.25 1.38
testing_score 85.0 0.20 17.00
documentation_score 75.0 0.15 11.25
practices_score 76.0 0.15 11.40
code_quality 60.7 0.10 6.07
Overall 1.00 56.1
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 6 High 27 Medium 41 Low 172 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 89 System graph 181 Crowd 0 Layer: Quality 28 Security 17 Software 95 Cicd 14 Frontend 62 Network 3 Hardware 1 Api 50

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.

Commented-out code 7 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
7 matching findings on this repo
  • info Commented-code block (6 lines) in integration/microservices/e2e/math-grpc.spec.…
  • info Commented-code block (9 lines) in integration/versioning/e2e/custom-versioning.…
  • info Commented-code block (5 lines) in integration/inspector/e2e/graph-inspector.spe…
  • info Commented-code block (5 lines) in packages/microservices/client/client-rmq.ts:39
  • info Commented-code block (5 lines) in packages/microservices/server/server-rmq.ts:43
  • info Commented-code block (5 lines) in packages/core/router/router-response-controll…
  • info Commented-code block (5 lines) in packages/core/test/injector/injector.spec.ts:…
View all commented-out code 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/30c176fa-1f87-4509-90b0-d3641fa6f6dc/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/30c176fa-1f87-4509-90b0-d3641fa6f6dc/

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.