Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo
24 of your 47 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

puppeteer/puppeteer

https://github.com/puppeteer/puppeteer · scanned 2026-06-05 06:50 UTC (6 days, 1 hour ago) · 10 languages

375 raw signals (41 security + 334 graph) 11/13 scanners ran 85th percentile · Typescript · medium (20-100K LoC) System graph score 63 (higher by 20)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 6 days, 1 hour ago · v2 · 180 actionable findings from 2 signal sources. 28 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
72.1
/100
Security checks
81
18 findings
System graph
63
88.9% cov · 162 findings
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 100.0 0.20 20.00
documentation_score 75.0 0.15 11.25
practices_score 66.0 0.15 9.90
code_quality 80.0 0.10 8.00
Overall 1.00 83.2
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 1 Medium 17 Low 115 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 18 System graph 162 Crowd 0 Layer: Quality 34 Security 5 Cicd 4 Software 51 Api 1 Frontend 83 Hardware 2

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 5 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
5 matching findings on this repo
  • info Commented-code block (10 lines) in test/src/oopif.test.ts:224
  • info Commented-code block (6 lines) in packages/puppeteer-core/src/injected/PQuerySe…
  • info Commented-code block (6 lines) in packages/puppeteer-core/src/cdp/TargetManager…
  • info Commented-code block (6 lines) in packages/puppeteer-core/src/cdp/NetworkManage…
  • info Commented-code block (6 lines) in tools/third_party/validate-licenses.ts:5
View all commented-out code findings →
Config drift 3 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
3 matching findings on this repo
  • low File has no detected symbols: prettier.config.js
  • low File has no detected symbols: puppeteer.config.js
  • critical Possible secret in website/docusaurus.config.js website/docusaurus.config.js:294
View all config drift findings →
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/33247712-bae1-4a0f-8b8c-22301afa739b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/33247712-bae1-4a0f-8b8c-22301afa739b/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.