yikart/AiToEarn
yikart/AiToEarnClick 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.
Compose service contains a literal secret environment value
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `yikart/AiToEarn` **Score: 47/100 (D+)** · 55 findings · scanned 2026-05-15 23:20 UTC · 249,488 LOC | Severity | Count | |---|---| | CRITICAL | 11 | | HIGH | 5 | | MEDIUM | 31 | | LOW | 5 | 📊 [Full filterable report](https://repobility.com/scan/fff94c6c-f7fb-435e-bc2c-eb71996272d3/) ·  ### Top findings 1. **CRITICAL** `SEC022` — Database URL With Embedded Credential `docker-compose.yml:30` · A07:2021 Identification & Authentication Failures 2. **CRITICAL** `DKC007` — Compose service contains a literal secret environment value `docker-compose.yml:167` 3. **CRITICAL** `DKC007` — Compose service contains a literal secret environment value `docker-compose.yml:111` 4. **CRITICAL** `DKC007` — Compose service contains a literal secret environment value `docker-compose.yml:75` 5. **CRITICAL** `DKC007` — Compose service contains a literal secret environment value `docker-compose.yml:52` --- **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/fff94c6c-f7fb-435e-bc2c-eb71996272d3/_
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.