playwright-api
Pass
Audited by Gen Agent Trust Hub on Jul 8, 2026
Risk Level: SAFECREDENTIALS_UNSAFEDATA_EXFILTRATION
Full Analysis
- [CREDENTIALS_UNSAFE]: Hardcoded dummy credentials are used in multiple code examples within the instructions.
- Evidence:
email: 'admin@example.com',password: 'AdminPass123!'found in thefixtures/api.fixture.tsand authentication testing snippets. - Evidence:
Authorization: 'Bearer admin-token-here'used in the advanced patterns section. - [DATA_EXFILTRATION]: Exposure to Indirect Prompt Injection (Category 8).
- Ingestion points: External API responses are ingested into the agent context via
response.json()in numerous test examples. - Boundary markers: Absent; there are no delimiters or instructions provided to ignore potentially malicious content embedded in the API responses.
- Capability inventory: The skill primarily uses Playwright's
expectlibrary for assertions; no critical capabilities likeeval()or arbitrarysubprocessexecution were detected in the data processing flow. - Sanitization: Absent; the code snippets parse raw JSON directly from network responses without sanitization.
- [SAFE]: The skill explicitly promotes security best practices in its documentation, advising users to 'Use environment variables -- Never hardcode URLs or credentials'.
- [SAFE]: The file upload example uses
path.resolveto restrict file access to the localtest-datadirectory.
Audit Metadata