ChromeDevTools/chrome-devtools-mcp
ChromeDevTools/chrome-devtools-mcpClick 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 docs site has no llms.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: `ChromeDevTools/chrome-devtools-mcp` **Score: 85/100 (A-)** · 8 findings · scanned 2026-05-14 21:41 UTC · 31,268 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 0 | | MEDIUM | 2 | | LOW | 4 | 📊 [Full filterable report](https://repobility.com/scan/421362e1-581f-4f46-a09d-07412d610e3f/) ·  ### Top findings 1. **MEDIUM** `WEB003` — Public web service has no security.txt `.well-known/security.txt` 2. **MEDIUM** `WEB015` — Public web app has no Content Security Policy `index.html` 3. **LOW** `WEB005` — robots.txt does not advertise a sitemap `tests/utils.ts` 4. **LOW** `WEB002` — Public web app has no sitemap `sitemap.xml` 5. **LOW** `WEB008` — Public docs site has no llms.txt `llms.txt` --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/421362e1-581f-4f46-a09d-07412d610e3f/_
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.