microsoft/playwright

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.

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

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 45.97s for a 66.4 MB repo slow.
Repobility's analysis ran in 14.58s after the clone landed.

https://github.com/microsoft/playwright · scanned 2026-06-05 06:57 UTC (6 days ago) · 10 languages

1554 raw signals (176 security + 1378 graph) 11/13 scanners ran 49th percentile · Typescript · huge (>500K LoC) System graph score 50 (higher by 35)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 6 days ago · v2 · 713 actionable findings from 2 signal sources. 152 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 · 652 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`	90.0	0.20	18.00
`documentation_score`	90.0	0.15	13.50
`practices_score`	79.0	0.15	11.85
`code_quality`	70.0	0.10	7.00
Overall		1.00	84.3

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 4 High 170 Medium 45 Low 323 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 61 System graph 652 Crowd 0 Layer: Quality 171 Security 27 Cicd 8 Software 60 Frontend 299 Api 148

Exclude dismissed / FP Exclude test files

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.

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Old/deprecated-named symbol `isBatchingLegacy` in tests/assets/reading-list/rea…

View all legacy markers findings →

Commented-out code 66 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/`.

12 matching findings on this repo

info Commented-code block (7 lines) in tests/library/har.spec.ts:113
info Commented-code block (5 lines) in tests/library/browsercontext-cookies-third-pa…
info Commented-code block (7 lines) in tests/library/events/prepend.spec.ts:4
info Commented-code block (7 lines) in tests/library/events/num-args.spec.ts:4
info Commented-code block (7 lines) in tests/library/events/add-listeners.spec.ts:4
info Commented-code block (7 lines) in tests/library/events/special-event-names.spec…
info Commented-code block (7 lines) in tests/library/events/subclass.spec.ts:4
info Commented-code block (7 lines) in tests/library/events/check-listener-leaks.spe…
info Commented-code block (7 lines) in tests/library/events/utils.ts:3
info Commented-code block (7 lines) in tests/library/events/symbols.spec.ts:4
info Commented-code block (7 lines) in tests/library/events/set-max-listeners-side-e…
info Commented-code block (7 lines) in tests/library/events/listeners.spec.ts:4

View all commented-out code findings →

Config drift 10 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.

10 matching findings on this repo

high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… utils/generate_chromium_default_font_families.js:76
low File has no detected symbols: tests/android/playwright.config.ts
low Stray `console.log` in TS/JS — tests/config/remote-server-impl.js:8
info TODO/FIXME marker in shipping code — tests/config/ghaMarkdownReporter.ts:25
low Stray `console.log` in TS/JS — tests/config/commonFixtures.ts:254
low Stray `console.log` in TS/JS — tests/playwright-test/expect-configure.spec.ts:82
low Stray `console.log` in TS/JS — tests/playwright-test/config.spec.ts:87
info TODO/FIXME marker in shipping code — packages/playwright/src/transform/tsconfig…
info Commented-code block (5 lines) in examples/todomvc/playwright.config.ts:72
info Commented-code block (5 lines) in examples/svgomg/playwright.config.ts:78

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/9bb00805-809e-47f5-9654-92e7f805606b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9bb00805-809e-47f5-9654-92e7f805606b/

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.