← Back to scan
File as GitHub Issue repo: apache/doris

Push this scan report to apache/doris

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

Code quality scan: 0 findings (D+, 47/100)

Issue body (markdown)

## Code-quality scan: `apache/doris`

**Score: 47/100 (D+)**  ·  0 findings  ·  scanned 2026-06-26 22:37 UTC  ·  0 LOC

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

📊 [Full filterable report](https://repobility.com/scan/6bc6e530-f738-4031-b245-811bd407411e/)  ·  ![scorecard](https://repobility.com/scan/6bc6e530-f738-4031-b245-811bd407411e/report.png?v=1782513432-s2)

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/6bc6e530-f738-4031-b245-811bd407411e/_
Already filed
'apache' is on the known-megaproject org list. These projects use auto-triage bots and established security disclosure channels. Unsolicited automated issues from Repobility would be perceived as AI-generated spam. For security findings, follow the project's SECURITY.md policy. For non-security findings, open a focused PR or community discussion instead.
Megaproject â high spam risk
Could not determine 'apache/doris' 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.