puppeteer/puppeteer

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.

24 of your 47 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

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

88.9% cov · 162 findings

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

Exclude dismissed / FP Exclude test files

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

Possible secret in website/docusaurus.config.js

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in website/docusaurus.config.js:294; move to env var / secrets manager.

website/docusaurus.config.js:294

Insecure pattern 'eval_used' in test-d/ElementHandle.test-d.ts:907

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

test-d/ElementHandle.test-d.ts:907

`dangerouslySetInnerHTML` used in a React component — website/src/theme/SearchPage/index.js:437

GapSeverity.MEDIUM Layer.FRONTEND score 0.360

Why: medium severity

Insecure pattern 'dangerous_innerhtml' in website/src/theme/SearchPage/index.js:437

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

website/src/theme/SearchPage/index.js:437

GitHub Actions workflow grants broad write permissions

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/ci.yml

GitHub Actions workflow grants broad write permissions

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/scorecards-analysis.yml

GitHub Actions workflow grants broad write permissions

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/pre-release.yml

GitHub Actions workflow grants broad write permissions

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/publish.yml

Dockerfile runs as root: docker/Dockerfile

GapSeverity.MEDIUM Layer.HARDWARE score 0.225

Why: medium severity

#10

`fetch()` without try/.catch or AbortSignal — packages/browsers/src/CLI.ts:544

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in packages/browsers/src/CLI.ts:544, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.