Habilidades playwright-cli Historial de auditorías
📦

Historial de auditorías

playwright-cli - 4 auditorías

Comparación de versiones

Cambios de capacidades y hallazgos entre versiones auditadas, primero las más recientes.

VersiónFechaResultadoElementos de revisiónCambio vs anterior
v4 Más reciente5 jul 2026, 23:10 10 confirmado0Sin cambios de capacidad
v3 5 jul 2026, 23:10 10 confirmado0 Contiene scripts
v2 30 jun 2026, 08:07 4 confirmado0Contiene scripts
v1 24 mar 2026, 08:23 Sin hallazgos confirmados1Base

5 jul 2026, 23:10

Most static findings are false positives from Markdown examples, placeholder URLs, and documented playwright-cli commands. Confirmed risks are limited to browser-session data operations and documented advanced capabilities such as run-code, tracing, and destructive session cleanup.

7
Archivos escaneados
1,149
Líneas analizadas
13
Elementos de revisión
0
Falsos positivos ignorados

Preocupaciones de seguridad confirmadas (10)

Medio
Arbitrary Playwright Code Execution
The skill documents run-code as a way to execute arbitrary Playwright code. This is powerful and expected, but it can read page data, grant permissions, or alter browser state on sensitive sites.
The documentation explicitly describes run-code for arbitrary Playwright code and shows direct browser context operations. The risk depends on user intent, but the capability is clear.
Medio
Browser Session Data Access
The skill supports reading, writing, deleting, saving, and restoring cookies and browser storage. These operations can expose or modify authentication state if used on real accounts.
The cited lines show cookie commands, stored cookies and localStorage values, and security notes about auth tokens. This confirms the session data exposure risk.
Medio
Trace Artifacts Can Capture Sensitive Data
Tracing captures request headers, bodies, DOM snapshots, screenshots, and console messages. The example flow enters payment-like values, so traces can store sensitive test or user data.
The documentation states traces include request and response bodies and shows a checkout capture flow. That directly supports the sensitive artifact risk.
Bajo
System reconnaissance
playwright-cli cookie-get session_id
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
System reconnaissance
playwright-cli cookie-delete session_id
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
System reconnaissance
playwright-cli cookie-get session_id
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
System reconnaissance
playwright-cli cookie-set session_id abc123
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
System reconnaissance
playwright-cli cookie-set session_id abc123 --domain=example.com --httpOnly --secure
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
System reconnaissance
playwright-cli cookie-delete session_id
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
Destructive Browser Session Controls
The skill documents commands that delete session data and forcefully kill browser processes. These commands are legitimate, but they can disrupt active work or remove useful state.
The cited commands explicitly delete user data, close browsers, and kill browser processes. The impact is operational disruption rather than malicious behavior.

Factores de riesgo

🌐 Acceso a red (34)
⚙️ Comandos externos (39)
📁 Acceso al sistema de archivos (1)

Patrones detectados

System reconnaissanceSystem reconnaissanceSystem reconnaissanceSystem reconnaissanceSystem reconnaissanceSystem reconnaissance
Auditado por: codex

5 jul 2026, 23:10

Most static findings are false positives from Markdown examples, placeholder URLs, and documented playwright-cli commands. Confirmed risks are limited to browser-session data operations and documented advanced capabilities such as run-code, tracing, and destructive session cleanup.

7
Archivos escaneados
1,149
Líneas analizadas
13
Elementos de revisión
0
Falsos positivos ignorados

Preocupaciones de seguridad confirmadas (10)

Medio
Arbitrary Playwright Code Execution
The skill documents run-code as a way to execute arbitrary Playwright code. This is powerful and expected, but it can read page data, grant permissions, or alter browser state on sensitive sites.
The documentation explicitly describes run-code for arbitrary Playwright code and shows direct browser context operations. The risk depends on user intent, but the capability is clear.
Medio
Browser Session Data Access
The skill supports reading, writing, deleting, saving, and restoring cookies and browser storage. These operations can expose or modify authentication state if used on real accounts.
The cited lines show cookie commands, stored cookies and localStorage values, and security notes about auth tokens. This confirms the session data exposure risk.
Medio
Trace Artifacts Can Capture Sensitive Data
Tracing captures request headers, bodies, DOM snapshots, screenshots, and console messages. The example flow enters payment-like values, so traces can store sensitive test or user data.
The documentation states traces include request and response bodies and shows a checkout capture flow. That directly supports the sensitive artifact risk.
Bajo
System reconnaissance
playwright-cli cookie-get session_id
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
System reconnaissance
playwright-cli cookie-delete session_id
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
System reconnaissance
playwright-cli cookie-get session_id
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
System reconnaissance
playwright-cli cookie-set session_id abc123
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
System reconnaissance
playwright-cli cookie-set session_id abc123 --domain=example.com --httpOnly --secure
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
System reconnaissance
playwright-cli cookie-delete session_id
The command can read, set, or delete browser cookies such as session_id, which may represent authentication state. This is documented functionality, but it is a real session data risk.
Bajo
Destructive Browser Session Controls
The skill documents commands that delete session data and forcefully kill browser processes. These commands are legitimate, but they can disrupt active work or remove useful state.
The cited commands explicitly delete user data, close browsers, and kill browser processes. The impact is operational disruption rather than malicious behavior.

Factores de riesgo

🌐 Acceso a red (34)
⚙️ Comandos externos (39)
📁 Acceso al sistema de archivos (1)

Patrones detectados

System reconnaissanceSystem reconnaissanceSystem reconnaissanceSystem reconnaissanceSystem reconnaissanceSystem reconnaissance
Auditado por: codex

30 jun 2026, 08:07

The static command findings are mostly false positives from markdown command examples, not Ruby backtick execution. The skill is still medium risk because it intentionally allows browser automation, arbitrary Playwright page code, network navigation, storage-state files, persistent profiles, and trace artifacts that can expose sensitive session data. No prompt injection attempt or confirmed malicious exfiltration path was found.

7
Archivos escaneados
1,149
Líneas analizadas
8
Elementos de revisión
3
Falsos positivos ignorados

Preocupaciones de seguridad confirmadas (4)

Medio
Browser Storage State Can Expose Sessions
The skill documents saving, loading, listing, and editing cookies, localStorage, sessionStorage, and authentication state files. This is legitimate for testing, but saved state can contain session tokens and must be protected.
The lines explicitly show state-save, state-load, cookie commands, and security notes about auth tokens. The context is legitimate automation, so the risk is exposure through misuse rather than confirmed malicious intent.
Medio
Arbitrary Playwright Code Execution in Browser Context
The skill supports run-code and eval commands that execute user supplied Playwright or JavaScript snippets in the active browser session. This enables advanced testing, but it can read page content, grant browser permissions, and manipulate storage.
The commands are directly documented and the examples show page evaluation and permission changes. The capability is expected for a Playwright CLI skill, but it increases impact if misused.
Medio
Trace and Video Artifacts May Capture Sensitive Data
Tracing records DOM snapshots, screenshots, network requests, headers, bodies, and console logs. Video recording and traces can preserve secrets typed during automated flows.
The reference states that traces capture network bodies, DOM snapshots, screenshots, and checkout form inputs. This is strong evidence of sensitive artifact risk without evidence of automatic exfiltration.
Medio
Persistent Browser Profiles Retain Local Data
The skill supports persistent sessions and custom profile directories. Persistent profiles can keep cookies, local storage, and other browser data beyond the immediate automation task.
The documented commands explicitly create persistent sessions and provide cleanup commands. The risk is manageable, but users must understand retention and delete data after sensitive workflows.
Falsos positivos estáticos ignorados (3)

Estas coincidencias estáticas fueron descartadas por la revisión semántica o coincidieron con tokens solo de esquema, por lo que se muestran por transparencia, pero no afectan la puntuación de calidad.

Bajo
Static External Command Matches Are Mostly Documentation Examples
The many Ruby or shell backtick detections occur in fenced markdown blocks that show playwright-cli usage. They are not Ruby backtick execution in source code, although the skill intentionally allows the playwright-cli command.
The cited locations are markdown command examples, not executable Ruby code. The allowed Bash wrapper is real, but the specific static Ruby backtick label is a false positive.
Bajo
Hardcoded URLs Are Example Targets
The hardcoded URL findings use documentation domains such as example.com and playwright.dev. I did not find evidence that these URLs receive secrets or hidden telemetry.
The URL examples are clearly part of user-facing command documentation and test workflows. No evidence found of a fixed third-party collection endpoint.
Bajo
Prompt Injection Search Found No Evidence
No reviewed file contained suspicious override language, fake system instructions, pre-approval claims, or requests to skip analysis.
Targeted review of the skill and references found no prompt injection phrases. The confidence is high, but this finding is limited to the files included in the audit.

Patrones detectados

Bash Tool Boundary Allows Playwright CLI Executionrun-code Provides Custom Automation LogicAuthentication Artifacts Are Written to Files
Auditado por: codex

24 mar 2026, 08:23

Static analysis flagged 289 patterns (187 external_commands, 51 network, 1 filesystem) but all are FALSE POSITIVES. The 'Ruby/shell backtick execution' patterns are markdown documentation examples, not actual code execution. Network findings are URLs in documentation for browser navigation examples. Browser credential/storage access is intentional functionality for testing authenticated workflows. This is a legitimate Microsoft Playwright CLI wrapper skill with appropriate tool scoping via allowed-tools directive.

8
Archivos escaneados
1,319
Líneas analizadas
4
Elementos de revisión
0
Falsos positivos ignorados
Elementos de revisión de capacidades (1)

Estas son capacidades locales reales que pueden esperarse para esta habilidad, por lo que requieren revisión, pero no se cuentan como comportamiento malicioso confirmado.

Bajo
External Command Execution Capability
Skill can execute arbitrary playwright-cli commands via Bash. This is by design but requires user trust in command outputs.

Factores de riesgo

⚙️ Comandos externos (1)
🌐 Acceso a red (1)
📁 Acceso al sistema de archivos (1)
Auditado por: claude