claude-howto

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.

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

Scan timing: clone 6.3s · analysis 48.59s · 15.3 MB · GitHub API rate-limit (preflight)

https://github.com/luongnv89/claude-howto.git · scanned 2026-06-03 04:06 UTC (2 days, 12 hours ago) · 10 languages

675 findings (157 legacy + 518 scanner) 45th percentile · Python · small (2-20K LoC) Scanner says 92 (lower by 26)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 days, 12 hours ago · v7 · 231 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	55.0	0.25	13.75
`testing_score`	72.0	0.20	14.40
`documentation_score`	100.0	0.15	15.00
`practices_score`	82.0	0.15	12.30
`code_quality`	36.5	0.10	3.65
Overall		1.00	65.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 10 High 110 Medium 25 Low 73 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 157 9-layer 74 Crowd 0 Layer: Software 68 Quality 108 Security 10 Api 1 Frontend 10 Cicd 34

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.

Fragile runtime 87 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).

12 matching findings on this repo

medium [COMP001] High cognitive complexity: Function `main` has cognitive complexity 1… scripts/check_cross_references.py:62
medium [COMP001] High cognitive complexity: Function `read_transcript` has cognitive c… 06-hooks/context-tracker.py:40
medium [COMP001] High cognitive complexity: Function `read_transcript` has cognitive c… 06-hooks/context-tracker-tiktoken.py:62
medium Bare except continues silently 03-skills/refactor/scripts/detect-smells.py:646
medium Bare except continues silently 03-skills/refactor/scripts/analyze-complexity.py:479
medium Bare except continues silently uk/03-skills/refactor/scripts/detect-smells.py:646
medium Bare except continues silently uk/03-skills/refactor/scripts/analyze-complexity.…:479
medium Bare except continues silently scripts/check_links.py:80
medium Agent control bridge may listen on a network interface without visible auth scripts/vendor_assets.py:1
medium Agent auto-approve or skip-permissions mode is easy to enable zh/QUICK_REFERENCE.md:100
medium Agent auto-approve or skip-permissions mode is easy to enable zh/INDEX.md:396
medium Agent auto-approve or skip-permissions mode is easy to enable ja/QUICK_REFERENCE.md:104

View all fragile runtime findings →

Config drift 7 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.

7 matching findings on this repo

high `self._config` used but never assigned in __init__ scripts/tests/test_build_website.py:410
high `self._config` used but never assigned in __init__ scripts/tests/test_build_website.py:391
high `self._config` used but never assigned in __init__ scripts/tests/test_build_website.py:372
high `self._config` used but never assigned in __init__ scripts/tests/test_build_website.py:352
high `self._config` used but never assigned in __init__ scripts/tests/test_build_website.py:332
high `self._config` used but never assigned in __init__ scripts/tests/test_build_website.py:313
low File has no detected symbols: scripts/website_templates/tailwind.config.js

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/8b67872a-a5da-4289-a507-147fcb4d2911/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8b67872a-a5da-4289-a507-147fcb4d2911/

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.