meyayl/docker-languagetool
meyayl/docker-languagetoolClick 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.
Workflow uses `secrets.DOCKERHUB_USERNAME` on a `pull_request` trigger
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `meyayl/docker-languagetool` **Score: 81/100 (A-)** · 18 findings · scanned 2026-06-05 21:06 UTC · 1,966 LOC | Severity | Count | |---|---| | CRITICAL | 9 | | HIGH | 2 | | MEDIUM | 3 | | LOW | 3 | 📊 [Full filterable report](https://repobility.com/scan/500a56ae-cf8c-4521-ac5c-5a7f25642ad9/) ·  ### Top findings 1. **CRITICAL** `MINED116` — Workflow uses `secrets.ANTHROPIC_API_KEY` on a `pull_request` trigger `.github/workflows/claude.yaml:165` · ✓ Repobility 2. **CRITICAL** `MINED116` — Workflow uses `secrets.ANTHROPIC_API_KEY` on a `pull_request` trigger `.github/workflows/claude.yaml:80` · ✓ Repobility 3. **CRITICAL** `MINED116` — Workflow uses `secrets.ANTHROPIC_API_KEY` on a `pull_request` trigger `.github/workflows/pipeline.yaml:449` · ✓ Repobility 4. **CRITICAL** `MINED116` — Workflow uses `secrets.DOCKERHUB_TOKEN` on a `pull_request` trigger `.github/workflows/pipeline.yaml:417` · ✓ Repobility 5. **CRITICAL** `MINED116` — Workflow uses `secrets.DOCKERHUB_USERNAME` on a `pull_request` trigger `.github/workflows/pipeline.yaml:416` · ✓ Repobility --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/500a56ae-cf8c-4521-ac5c-5a7f25642ad9/_
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.