A high-level API to automate web browsers
87%
Total Score
healthy
Active Microsoft-backed maintenance is offset slightly by workflow permissions and package-to-repository naming ambiguity.
Publishing access is primarily associated with microsoft.com and the project has organizational backing. The two gmail.com publisher accounts, pavelfeldman and yurys, are account-hygiene cautions but do not by themselves indicate limited maintenance capacity.
The repository name does not match playwright-core and its README does not mention the package, creating some ambiguity about package-to-repository mapping. The package README identifies it as a Playwright component, so this is a limited caution rather than a severe concern.
All 21 workflows were analyzed with no untrusted checkout or script-injection findings, and all 79 action references are pinned. High-confidence github-app findings involving blanket app-token permissions and medium-confidence secrets-inherit findings are workflow hygiene concerns; the template-injection findings lack a corroborating untrusted trigger or sink.
We didn't find any vulnerabilities for this package.
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.