Anduin2017/HowToCook

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.

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

Scan timing: clone 2.89s · analysis 6.1s · 1.8 MB · GitHub API rate-limit (preflight)

https://github.com/Anduin2017/HowToCook · scanned 2026-06-05 06:05 UTC (10 hours, 12 minutes ago) · 10 languages

22 findings (12 legacy + 10 scanner) 67th percentile · Javascript · tiny (<2K LoC) Scanner says 100 (lower by 26)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 10 hours, 12 minutes ago · v2 · 17 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`	50.0	0.15	7.50
`security_score`	100.0	0.25	25.00
`testing_score`	70.0	0.20	14.00
`documentation_score`	60.0	0.15	9.00
`practices_score`	72.0	0.15	10.80
`code_quality`	70.0	0.10	7.00
Overall		1.00	73.3

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 5 Medium 4 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 12 9-layer 5 Crowd 0 Layer: Security 2 Software 7 Quality 5 Api 1 Frontend 2

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 4 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).

4 matching findings on this repo

info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… .github/readme-generate.js:83
info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… .github/manual_lint.js:18
info [MINED043] Http Not Https: Hardcoded http:// (not localhost) for endpoints that… .github/manual_lint.js:255
high [SEC085] JS: child_process.exec with non-literal: child_process.exec with user-… .github/manual_lint.js:223

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/8cf0cce4-04a4-4817-a888-165c305c0a5f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8cf0cce4-04a4-4817-a888-165c305c0a5f/

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.