playwright-stealth-verify
Verify Automated Browser Fingerprints
Automated browsers can expose inconsistent fingerprints that weaken test reliability. This skill measures those inconsistencies with liarjs and explains the failing checks.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "playwright-stealth-verify" from https://skillstore.io/skills/liarjsdev-playwright-stealth-verify.md and its manifest at https://skillstore.io/api/skills/liarjsdev-playwright-stealth-verify/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "playwright-stealth-verify". Check this Playwright Page offline and explain the result.
Expected outcome:
- Overall result: weak fingerprint consistency.
- The webdriver and headless user-agent checks failed.
- No external network request was made.
- Review launch settings before setting a test threshold.
Using "playwright-stealth-verify". Review the browser on my confirmed local CDP endpoint.
Expected outcome:
The browser is reachable and the client signals are mostly coherent. Worker identity differs from the main thread, indicating a partial override.
Using "playwright-stealth-verify". Suggest a continuous integration assertion from this stable baseline.
Expected outcome:
Require a score of at least 85 and fail when webdriver, native integrity, or worker consistency reports a bad status.
Security Audit
Medium RiskMost static findings confuse Markdown backticks with shell execution or flag documentation as reconnaissance. Four findings are confirmed because the skill runs external packages or sends fingerprint data to liarjs.dev. Contextual review also identified CDP session access and browser detection-evasion assessment as dual-use risks.
Confirmed security concerns (2)
Capability review items (5)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (32)
🌐 Network access (6)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/liarjsdev-playwright-stealth-verify/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/liarjsdev-playwright-stealth-verify?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/liarjsdev-playwright-stealth-verify?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/liarjsdev-playwright-stealth-verify/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/liarjsdev-playwright-stealth-verify.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
liarjsdev. (2026). playwright-stealth-verify security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/liarjsdev-playwright-stealth-verify/audits/1BibTeX citation
@techreport{liarjsdev-liarjsdev-playwright-stealth-verify-2026,
author = {liarjsdev},
title = {playwright-stealth-verify security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/liarjsdev-playwright-stealth-verify/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "playwright-stealth-verify security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "liarjsdev"
date-released: "2026-08-08"
url: "https://skillstore.io/skills/liarjsdev-playwright-stealth-verify/audits/1"
identifiers:
- type: other
value: "skillstore:liarjsdev-playwright-stealth-verify:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Validate Test Browser Configuration
Measure fingerprint consistency before automated browser tests run in continuous integration.
Audit a Custom Chromium Build
Attach to a local CDP endpoint and identify inconsistent browser identity signals.
Review Automation Fingerprint Regressions
Compare failed check identifiers after launch flags, plugins, or proxies change.
Try These Prompts
Check my Playwright browser fingerprint offline. Explain the score and list the failed checks without changing the browser.
Use liarjs checkPage with my existing Page object. Summarize fingerprint inconsistencies and suggest test assertions.
After I confirm ownership, audit the browser at my local CDP endpoint. Do not visit third-party pages or modify the profile.
Analyze my baseline and current fingerprint results. Propose score and check-level gates that detect meaningful regressions while limiting false failures.
Best Practices
- Use offline mode when external network observation is unnecessary.
- Confirm CDP endpoint ownership and use an isolated browser profile.
- Pin liarjs to an exact reviewed version in the project lockfile.
Avoid
- Do not attach to an unknown CDP endpoint or an active personal browsing profile.
- Do not send fingerprint data to an external endpoint without consent.
- Do not treat a high score as permission to bypass third-party access controls.