← Back to scan
File as GitHub Issue repo: 51ayushsharma-cloud/aditya-boost-backend

Push this scan report to 51ayushsharma-cloud/aditya-boost-backend

Click 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.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

No Repobility access matrix policy found

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
HIGH SEC135 [SEC135] Auth/permission check missing on AI-generated endpoint: Mutating HTTP endpoint g… app.py:23
HIGH CORE_NO_TESTS No test files found —
MED CFG006 [CFG006] Missing .gitignore: No .gitignore file. Risk of committing secrets and build art… —
MED SEC123 [SEC123] Production stack trace / debug output exposed: Debug mode left on in production … app.py:47
MED AUC001 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks… —
MED WEB003 Public web service has no security.txt .well-known/security.txt
MED AUC002 [AUC002] Low visible authorization coverage in route inventory: Only 0.0% of discovered r… —
MED CORE_NO_CI No CI/CD configuration found —
MED CORE_NO_README No README file found —
LOW AUC005 [AUC005] No authorization-focused tests detected: No test files with common authorization… —
LOW CORE_NO_LICENSE No LICENSE file —
INFO MINED069 [MINED069] Debug True Prod: Django/Flask DEBUG=True or app.debug=True in non-test files. app.py:47
Reset to top 5 12 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `51ayushsharma-cloud/aditya-boost-backend`

**Score: 63/100 (D)**  ·  12 findings  ·  scanned 2026-05-27 14:03 UTC  ·  47 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 2 |
| MEDIUM | 7 |
| LOW | 2 |

📊 [Full filterable report](https://repobility.com/scan/65129156-d7b4-4dfa-a1d1-37d000c3d85e/)  ·  ![scorecard](https://repobility.com/scan/65129156-d7b4-4dfa-a1d1-37d000c3d85e/report.png?v=1779890596-s2)

### Top findings

1. **HIGH** `SEC135` — Auth/permission check missing on AI-generated endpoint
   `app.py:23` · CWE-862
2. **HIGH** `CORE_NO_TESTS` — No test files found
3. **MEDIUM** `CFG006` — Missing .gitignore
4. **MEDIUM** `SEC123` — Production stack trace / debug output exposed
   `app.py:47` · A09:2021 Security Logging & Monitoring Failures
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/65129156-d7b4-4dfa-a1d1-37d000c3d85e/_
Premium account
This scan was submitted by a Enterprise-tier account. Premium accounts have full outreach control â Repobility doesn't pre-fill the 'file as GitHub issue' button for paid users. You can still file the issue manually using the markdown body above (Copy markdown), or contact us if you'd like batch-filing enabled for your account.
Megaproject â high spam risk
Could not determine '51ayushsharma-cloud/aditya-boost-backend' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
Cancel

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.