← Back to scan
File as GitHub Issue repo: vlang/vc

Push this scan report to vlang/vc

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

Detected a Generic API Key, potentially exposing access to various services and sensitive

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
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… v.c:172286
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… v_win.c:163758
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… v.c:154425
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… v_win.c:146014
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… v.c:128597
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… v_win.c:120320
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… v.c:95145
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… v_win.c:87315
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… v.c:72017
CRIT generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive… v_win.c:64382
MED CFG006 [CFG006] Missing .gitignore: No .gitignore file. Risk of committing secrets and build art… —
LOW CORE_NO_LICENSE No LICENSE file —
Reset to top 5 12 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `vlang/vc`

**Score: 66/100 (C-)**  ·  12 findings  ·  scanned 2026-06-05 21:27 UTC  ·  0 LOC

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

📊 [Full filterable report](https://repobility.com/scan/2cdfe7fc-96f9-44dd-a5a4-7126acd085ee/)  ·  ![scorecard](https://repobility.com/scan/2cdfe7fc-96f9-44dd-a5a4-7126acd085ee/report.png?v=1780694860-s2)

### Top findings

1. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive 
   `v.c:172286`
2. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive 
   `v_win.c:163758`
3. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive 
   `v.c:154425`
4. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive 
   `v_win.c:146014`
5. **CRITICAL** `generic-api-key` — Detected a Generic API Key, potentially exposing access to various services and sensitive 
   `v.c:128597`

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/2cdfe7fc-96f9-44dd-a5a4-7126acd085ee/_
Megaproject â high spam risk
Could not determine 'vlang/vc' 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.
Open in GitHub to file this 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.