puneetv503-dot/smartdukan-backend

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.

Scan timing: clone 1.14s · analysis 0.07s · GitHub API rate-limit (preflight)

https://github.com/puneetv503-dot/smartdukan-backend.git · scanned 2026-05-26 07:22 UTC (1 week, 3 days ago) · 10 languages

29 findings (15 legacy + 14 scanner) 50th percentile · Python · tiny (<2K LoC)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 3 days ago · v2 · 22 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`	30.0	0.15	4.50
`security_score`	95.5	0.25	23.88
`testing_score`	70.0	0.20	14.00
`documentation_score`	25.0	0.15	3.75
`practices_score`	72.0	0.15	10.80
`code_quality`	80.0	0.10	8.00
Overall		1.00	64.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 12 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 15 9-layer 7 Crowd 0 Layer: Quality 7 Security 6 Software 5 Frontend 1 Cicd 1 Api 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

medium Public web service has no security.txt .well-known/security.txt
medium Bare except continues silently main.py:61
high [SEC135] Auth/permission check missing on AI-generated endpoint: Mutating HTTP … main.py:28
high FastAPI POST /scan-bill has no auth main.py:29

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/31db1c59-78ea-4993-99fb-4dadeda5541c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/31db1c59-78ea-4993-99fb-4dadeda5541c/

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.