chrome-php/chrome vulnerabilities
Instrument headless chrome/chromium instances from PHP
- Registry
- Composer
- Latest
- 1.16.2
- License
- MIT
1 known advisory
The latest version, 1.16.2, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require chrome-php/chrome:^1.16.2Is your project on an affected chrome-php/chrome?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for chrome-php/chrome
Chrome PHP is missing encoding in `CssSelector`
- Affected
- <1.14.0
- Fixed in
- 1.14.0
Is your chrome-php/chrome version vulnerable?
- chrome-php/chrome 1.16No known advisories in 1.16.2
- chrome-php/chrome 1.15No known advisories in 1.15.1
- chrome-php/chrome 1.14No known advisories in 1.14.0
- chrome-php/chrome 1.131 advisory in 1.13.0
- chrome-php/chrome 1.121 advisory in 1.12.1
- chrome-php/chrome 1.111 advisory in 1.11.0
- chrome-php/chrome 0.111 advisory in 0.11.2
- chrome-php/chrome 0.101 advisory in 0.10.0
- chrome-php/chrome 0.91 advisory in 0.9.0
- chrome-php/chrome 0.81 advisory in 0.8.1
- chrome-php/chrome 0.71 advisory in 0.7.0
- chrome-php/chrome 0.61 advisory in 0.6.0
Which of your client projects still run an old chrome-php/chrome?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.