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

HKUDS/nanobot

https://github.com/HKUDS/nanobot · scanned 2026-05-15 05:01 UTC (3 weeks ago) · 10 languages

152 findings (34 legacy + 118 scanner) 44th percentile · Python · large (100-500K LoC) Scanner says 78 (lower by 5)

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

Complete repo analysis

Last scanned 3 weeks ago · v1 · 27 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
70.0
/100
Repobility
62
27 legacy
9-layer
78
100.0% cov · 0 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-17-v4 calibration-aware
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 54.4 0.25 13.60
testing_score 100.0 0.20 20.00
documentation_score 85.0 0.15 12.75
practices_score 75.0 0.15 11.25
code_quality 59.0 0.10 5.90
Overall 1.00 72.5
Calibrated penalty buckets (security_score): web: 1.6 · agent: 5.8 · docker: 9.5 · threat: 28.8
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 16 Medium 2 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 27 9-layer 0 Crowd 0 Layer: Quality 9 Security 9 Cicd 9

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.

Fragile runtime 9 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
9 matching findings on this repo
  • medium Public web service has no security.txt .well-known/security.txt
  • medium localStorage write failures are swallowed silently webui/src/lib/bootstrap.ts:18
  • medium localStorage write failures are swallowed silently webui/src/i18n/config.ts:80
  • medium localStorage write failures are swallowed silently webui/src/hooks/useTheme.ts:36
  • medium localStorage write failures are swallowed silently webui/src/App.tsx:259
  • medium Agent auto-approve or skip-permissions mode is easy to enable nanobot/skills/tmux/SKILL.md:81
  • medium Duplicated implementation block across source files nanobot/providers/bedrock_provider.py:620
  • medium Duplicated implementation block across source files nanobot/providers/bedrock_provider.py:619
  • medium Duplicated implementation block across source files nanobot/providers/azure_openai_provider.py:117
View all fragile runtime 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/9cb48be6-42ed-41b5-8e46-4312e8f96321/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9cb48be6-42ed-41b5-8e46-4312e8f96321/

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.