ros/rosdistro
ros/rosdistroClick 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.
Public web service has no security.txt
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `ros/rosdistro` **Score: 81/100 (B+)** · 5 findings · scanned 2026-05-15 16:00 UTC · 4,528 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 1 | | MEDIUM | 3 | | LOW | 0 | 📊 [Full filterable report](https://repobility.com/scan/426fecd2-3115-406b-a69e-ea1e3bfadd3e/) ·  ### Top findings 1. **HIGH** `SEC004` — SQL Injection Risk `migration-tools/migrate-rosdistro.py:33` · A03:2021 Injection 2. **MEDIUM** `ERR001` — Silent Exception Swallowing `scripts/check_rosdep.py:173` 3. **MEDIUM** `AIC003` — Duplicated implementation block across source files `scripts/check_rosdistro.py:1` 4. **MEDIUM** `WEB003` — Public web service has no security.txt `.well-known/security.txt` --- **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/426fecd2-3115-406b-a69e-ea1e3bfadd3e/_
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.