← Back to scan
File as GitHub Issue repo: punitarani/fli

Push this scan report to punitarani/fli

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

Duplicated implementation block across source files

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 DKR006 Dockerfile pipes a remote script into a shell .devcontainer/Dockerfile:11
MED DKR003 Compose service `fli-mcp` image uses the latest tag docker-compose.yml:1
MED AUC001 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks… —
MED AIC003 Duplicated implementation block across source files fli/models/google_flights/flights.py:7
MED AIC003 Duplicated implementation block across source files fli/models/google_flights/__init__.py:23
MED AIC003 Duplicated implementation block across source files fli/cli/commands/multi.py:53
MED AIC003 Duplicated implementation block across source files fli/cli/commands/flights.py:337
MED DKR001 Docker final stage has no non-root USER .devcontainer/Dockerfile:1
MED WEB003 Public web service has no security.txt .well-known/security.txt
MED DKR014 Dockerfile copies broad context with incomplete .dockerignore .devcontainer/Dockerfile:29
MED AGT012 Agent control bridge may listen on a network interface without visible auth fli/mcp/server.py:38
LOW DKR008 .dockerignore misses sensitive defaults .dockerignore
LOW DKC010 Compose service lacks no-new-privileges hardening docker-compose.yml:1
LOW DKC006 Compose service does not declare a runtime user docker-compose.yml:1
Reset to top 5 14 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `punitarani/fli`

**Score: 81/100 (A-)**  ·  15 findings  ·  scanned 2026-05-16 04:22 UTC  ·  27,122 LOC

| Severity | Count |
|---|---|
| CRITICAL | 0 |
| HIGH | 1 |
| MEDIUM | 10 |
| LOW | 3 |

📊 [Full filterable report](https://repobility.com/scan/3f04d0f4-c7f5-408a-b938-5c6db9e63ea0/)  ·  ![scorecard](https://repobility.com/scan/3f04d0f4-c7f5-408a-b938-5c6db9e63ea0/report.png?v=1778905324-s2)

### Top findings

1. **HIGH** `DKR006` — Dockerfile pipes a remote script into a shell
   `.devcontainer/Dockerfile:11`
2. **MEDIUM** `DKR003` — Compose service `fli-mcp` image uses the latest tag
   `docker-compose.yml:1`
3. **MEDIUM** `AUC001` — No Repobility access matrix policy found
   CWE-285 · WSTG-AUTHZ
4. **MEDIUM** `AIC003` — Duplicated implementation block across source files
   `fli/models/google_flights/flights.py:7`
5. **MEDIUM** `AIC003` — Duplicated implementation block across source files
   `fli/models/google_flights/__init__.py:23`

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/3f04d0f4-c7f5-408a-b938-5c6db9e63ea0/_
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 'punitarani/fli' 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.
I read the warnings â override 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.