← Home

@cloudflare/puppeteer

npm Repository Homepage
5
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

cf-ci-writedash_service_accountwrangler-publishercfprivengcf-npm-publish

Keywords

puppeteerchromeheadlessautomation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Base64 decoding is used for screenshot/PDF data handling — standard Puppeteer API behavior. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in ScreenRecorder for ffmpeg — documented, expected functionality. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function() used to serialize/deserialize functions for browser execution — core Puppeteer pattern. ai

Versions (showing 5 of 5)

Version Deps Published
1.2.0 4 / 7
1.1.0 4 / 7
1.0.7 4 / 7
1.0.6 4 / 7
1.0.5 4 / 7

v1.2.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: celso → GitHub Actions (on 2026-07-27, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (celso) on 2026-07-27, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v1.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.