Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Hold on, we're currently generating a fresh version of this report
Generated on Apr 15, 2024 via pnpm

puppeteer-core 21.2.1

A high-level API to control headless Chrome over the DevTools Protocol
Package summary
Share
0
issues
6
licenses
63
MIT
8
ISC
6
BSD-2-Clause
10
other licenses
Apache-2.0
5
BSD-3-Clause
4
0BSD
1
Package created
10 Aug 2018
Version published
13 Sep 2023
Maintainers
2
Total deps
87
Direct deps
6
License
Apache-2.0

Issues

0
This package has no issues

Licenses

MIT License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
Cannot
hold-liable
Must
include-copyright
include-license
63 Packages, Including:
@tootallnate/quickjs-emscripten@0.23.0
@types/node@20.12.7
@types/yauzl@2.10.3
agent-base@7.1.1
ansi-regex@5.0.1
ansi-styles@4.3.0
ast-types@0.13.4
base64-js@1.5.1
basic-ftp@5.0.5
buffer-crc32@0.2.13
buffer@5.7.1
color-convert@2.0.1
color-name@1.1.4
cross-fetch@4.0.0
data-uri-to-buffer@6.0.2
debug@4.3.4
degenerator@5.0.1
emoji-regex@8.0.0
end-of-stream@1.4.4
escalade@3.1.2
fast-fifo@1.3.2
fd-slicer@1.1.0
fs-extra@11.2.0
get-stream@5.2.0
get-uri@6.0.3
http-proxy-agent@7.0.2
https-proxy-agent@7.0.4
ip-address@9.0.5
is-fullwidth-code-point@3.0.0
jsbn@1.1.0
jsonfile@6.1.0
mitt@3.0.1
mkdirp-classic@0.5.3
ms@2.1.2
netmask@2.0.2
node-fetch@2.7.0
pac-proxy-agent@7.0.1
pac-resolver@7.0.1
pend@1.2.0
progress@2.0.3
proxy-agent@6.3.1
proxy-from-env@1.1.0
pump@3.0.0
queue-tick@1.0.1
require-directory@2.1.1
smart-buffer@4.2.0
socks-proxy-agent@8.0.3
socks@2.8.3
streamx@2.16.1
string-width@4.2.3

ISC License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
Cannot
hold-liable
Must
include-copyright
include-license
8 Packages, Including:
cliui@8.0.1
get-caller-file@2.0.5
graceful-fs@4.2.11
lru-cache@7.18.3
once@1.4.0
wrappy@1.0.2
y18n@5.0.8
yargs-parser@21.1.1

BSD 2-Clause "Simplified" License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
place-warranty
Cannot
hold-liable
Must
include-copyright
include-license
6 Packages, Including:
escodegen@2.1.0
esprima@4.0.1
estraverse@5.3.0
esutils@2.0.3
extract-zip@2.0.1
webidl-conversions@3.0.1

Apache License 2.0

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
use-patent-claims
place-warranty
Cannot
hold-liable
use-trademark
Must
include-copyright
include-license
state-changes
include-notice
5 Packages, Including:
@puppeteer/browsers@1.7.1
b4a@1.6.6
bare-events@2.2.2
chromium-bidi@0.4.26
puppeteer-core@21.2.1

BSD 3-Clause "New" or "Revised" License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
place-warranty
Cannot
use-trademark
hold-liable
Must
include-copyright
include-license
4 Packages, Including:
devtools-protocol@0.0.1159816
ieee754@1.2.1
source-map@0.6.1
sprintf-js@1.1.3

BSD Zero Clause License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
include-copyright
include-license
include-original
Cannot
hold-liable
Must
1 Packages, Including:
tslib@2.6.2
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

6
All Dependencies CSV
β“˜ This is a list of puppeteer-core 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities
@puppeteer/browsers1.7.158.93 kBApache-2.0
prod
chromium-bidi0.4.26480.99 kBApache-2.0
prod
cross-fetch4.0.021.36 kBMIT
prod
debug4.3.412.94 kBMIT
prod
devtools-protocol0.0.1159816381.9 kBBSD-3-Clause
prod peer
ws8.14.131.85 kBMIT
prod

Visualizations

Frequently Asked Questions

What does puppeteer-core do?

Puppeteer-core is a Node.js library providing a high-level API to control Chrome or Chromium browsers over the DevTools Protocol. This powerful tool enables you to programmatically manipulate the browser to automate tasks such as form submissions, UI testing, PDF and screenshot generation, server-side rendering for Single-Page Applications (SPAs), and much more. To ensure seamless operation, puppeteer-core doesn't make assumptions about any defaults and will not download Chrome or any other browser upon installation.

How do you use puppeteer-core?

Using puppeteer-core in your JavaScript project conveniently affords you the power of full browser automation. First, start by installing puppeteer-core in your project using npm:

npm i puppeteer-core

Once installed, you can start utilizing its functions. Here is a brief example of how to use puppeteer-core to automate a task:

const puppeteer = require('puppeteer-core');

(async () => {
  const browser = await puppeteer.launch({executablePath: '/path/to/Chrome'});
  const page = await browser.newPage();
  await page.goto('https://example.com');
  await page.screenshot({path: 'example.png'});
  await browser.close();
})();

In this example, we first import the puppeteer-core library. We then launch the browser, open a new page, navigate to an example website, take a screenshot of the page, and finally close the browser.

Remember, for puppeteer-core, you need to provide the path to the browser executable in the launch method. The above example also implies that you have already installed a compatible browser in your system.

Where are the puppeteer-core docs?

You can explore the rich features of puppeteer-core further by accessing its complete documentation and API at https://pptr.dev/api. This site provides comprehensive guides, usage examples, and a helpful FAQ section to assist you in making the most of this powerful browser automation library.