puppeteer@25.14.0
A high-level API to control headless Chrome over the DevTools Protocol
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection ties the postinstall hook to supported browser installation and the CLI to browser management. The inspected entrypoints and configuration reveal no concrete attack behavior.
Decision evidence
public snapshot- The manifest’s postinstall hook runs the package’s install script.
- The install script calls Puppeteer’s browser download routine.
- The routine invokes the browser installer with a browser, cache directory, and build identifier.
- The installer returns early when the configured global download-skip setting is enabled.
- The main module exports the Puppeteer Core API and initializes package configuration.
- The CLI delegates browser management to a browser-focused command using Puppeteer’s configured cache.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgThe manifest’s postinstall hook runs the package’s install script.
package.jsonView on unpkg · L42Findings
Affected versions and remediation
This report applies to puppeteer@25.14.0.
See all versions of puppeteer for other recorded verdicts.
- Review the evidence and your use of puppeteer@25.14.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.