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

Scan timing: clone 1.15s · analysis 0.37s · 0.2 MB · GitHub API rate-limit (preflight)

microsoft/playwright-mcp

https://github.com/microsoft/playwright-mcp · scanned 2026-05-31 01:27 UTC (5 days, 8 hours ago) · 10 languages

235 findings (19 legacy + 216 scanner) 89th percentile · Typescript · tiny (<2K LoC) Scanner says 81 (higher by 11)

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

Complete repo analysis

Last scanned 5 days, 8 hours ago · v9 · 44 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
88.7
/100
Repobility
97
19 legacy
9-layer
81
77.8% cov · 25 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 98.7 0.25 24.68
testing_score 90.0 0.20 18.00
documentation_score 88.0 0.15 13.20
practices_score 84.0 0.15 12.60
code_quality 78.9 0.10 7.89
Overall 1.00 91.4
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 16 Medium 8 Low 16 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 19 9-layer 25 Crowd 0 Layer: Cicd 11 Quality 3 Software 23 Api 1 Frontend 4 Hardware 2

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

#1
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/ci.yml:60
#2
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/ci.yml:62
#3
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish.yml:121
#4
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish.yml:123
#5
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish.yml:125
#6
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish.yml:134
#7
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish.yml
#8
Stray `console.log` in TS/JS — roll.js:14
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in roll.js:14.
#9
Stray `console.log` in TS/JS — update-readme.js:125
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in update-readme.js:125.
#10
Docker base image is tag-pinned but not digest-pinned: node:22-bookworm-slim
GapSeverity.LOW Layer.HARDWARE score 0.100
Why: low severity
Dockerfile:8

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/3dd9583b-365f-4038-a5b9-ae84414fbb96/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3dd9583b-365f-4038-a5b9-ae84414fbb96/

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.