a public repository, read by nittim

ChromeDevTools/chrome-devtools-mcp security audit

What nittim read in this repository, and what it found. Public repository, public reading — sourced from its own code and dependency manifests, nothing else.

Chrome DevTools for coding agents

TypeScript · 54.7k stars · last push November 2, 2026

ChromeDevTools/chrome-devtools-mcp is a TypeScript repository that provides Chrome DevTools functionality for coding agents. The project enables developers to integrate browser debugging capabilities into automated coding workflows and agent systems.

Nittim scanned 338 files in the repository and found evidence of committed credentials on production paths. No vulnerable runtime dependencies were detected during the scan.

Developers should rescan ChromeDevTools/chrome-devtools-mcp after removing the committed credentials from production paths. Running an audit will provide detailed information about the credential exposure and help ensure the issue is fully resolved.

Written from nittim's own scan on November 3, 2026; rescanned when the repository changes.

No verdict. The rule-based check reports hard evidence, or reports that it found none. Neither is a judgment on whether this code is safe to ship.

What was read — rule-based scan

Rule-based checks run on nittim's servers — a secret scanner and a dependency check, no model in the path. The code reached those two and stopped there.

Read 338 of 338 eligible files. Commit aade3be. 2026-11-03.

What the scanners found

Committed secrets on production paths
1
Vulnerable runtime dependencies
0

Run it yourself

Scan any public repository in seconds — no sign-in, no card. Audit it to have a model read the code. Loop the report into your assistant to get the fixes applied and re-checked.

Scan your own repo

Questions

What did nittim read in ChromeDevTools/chrome-devtools-mcp?
nittim read 338 of 338 eligible files in ChromeDevTools/chrome-devtools-mcp. The reading ran on November 3, 2026. It was taken at commit aade3be.
Did nittim find committed secrets or vulnerable dependencies in ChromeDevTools/chrome-devtools-mcp?
The rule-based scan found 1 committed secret and 0 vulnerable dependencies in ChromeDevTools/chrome-devtools-mcp. No vulnerable dependency was found by the rule-based scan.
Is ChromeDevTools/chrome-devtools-mcp production ready?
A free scan is not a verdict. A full audit gives one.

More like this

More TypeScript repositories →

Add the badge to your README
README badge
nittim verdict badge for ChromeDevTools/chrome-devtools-mcp[![nittim](https://nittim.com/api/badge/ChromeDevTools/chrome-devtools-mcp)](https://nittim.com/library/ChromeDevTools/chrome-devtools-mcp)