Security policy
The Puppeteer project takes security very seriously. Please use [Chromium’s process to report security issues](https://www.chromium.org/Home/chromium-security/reporting-security-bugs/).
Loading actions...
Skill content
Main instructions and any bundled files for this skill.
Security policy
The Puppeteer project takes security very seriously. Please use Chromium’s process to report security issues.
Scope
Puppeteer provides powerful capabilities for browser installation, automation, and inspection, and it is the responsibility of the calling code to ensure these are used safely and as intended.
Several APIs in this project have the ability to perform actions such as writing files to disk (e.g. via browser downloads or screenshots) or dynamically loading Chrome extensions. These are intentional, documented features and are not vulnerabilities. Specifically, Man-in-the-Middle (MITM) attacks and the manipulation of Puppeteer or browser downloads via local access are not considered vulnerabilities.
We appreciate feedback and suggestions from developers on how this tool can make it easier for them to build a more secure user experience, but will treat these exclusively as feature requests, and not vulnerabilities in Puppeteer itself.
Related Skills
Frontend Typescript Linting.mdc
TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...
2. Apply Deepthink Protocol (reason about dependencies
risks