puneetv503-dot/smartdukan-backend
puneetv503-dot/smartdukan-backendClick the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
No Repobility access matrix policy found
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `puneetv503-dot/smartdukan-backend` **Score: 64/100 (C+)** · 15 findings · scanned 2026-05-26 07:22 UTC · 62 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 2 | | MEDIUM | 11 | | LOW | 2 | 📊 [Full filterable report](https://repobility.com/scan/31db1c59-78ea-4993-99fb-4dadeda5541c/) ·  ### Top findings 1. **HIGH** `SEC135` — Auth/permission check missing on AI-generated endpoint `main.py:28` · CWE-862 2. **HIGH** `MINED112` — FastAPI POST /scan-bill has no auth `main.py:29` · ✓ Repobility 3. **MEDIUM** `CFG006` — Missing .gitignore 4. **MEDIUM** `MINED111` — Bare except continues silently `main.py:61` · ✓ Repobility 5. **MEDIUM** `AUC001` — No Repobility access matrix policy found CWE-285 · WSTG-AUTHZ --- **Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately. --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/31db1c59-78ea-4993-99fb-4dadeda5541c/_
The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.
For real security findings on big repos: use the project's SECURITY.md or
private advisory flow instead of a public issue.