npm package

chromedriver

136.0.2

Default version

Published

Description

ChromeDriver for Selenium

Attestations

SLSA Provenance Attestation
This version has a SLSA provenance attestation.
VERIFIEDThe Sigstore bundle containing this attestation was verified using sigstore-go.

Repository
github.com/giggio/node-chromedriver (ec2c1)
Build config
github.com/giggio/node-chromedriver/.github/workflows/build.yml
Built by
GHA on GitHub
Log date
The time this entry was integrated into the rekor transparency log.
(index 213214046)
Workflow run
15035079457
SLSA Version
1
To verify the attestation, run the "npm audit signatures" command or download the attestations bundle from NPM and use the slsa-verifier tool.

Links

Origin
Homepage
Repo
Issues
Attestations

Projects

giggio/node-chromedriver

GitHub

An installer and wrapper for Chromedriver.

 188 forks
 486 stars

OpenSSF scorecard

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

View information about checks and how to fix failures.

Score
3.8/10
Scorecard as of .
Maintained
10/10
Determines if the project is "actively maintained".
Reasoning
28 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow
0/10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning
dangerous workflow patterns detected
Code-Review
1/10
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning
Found 1/10 approved changesets -- score normalized to 1
Binary-Artifacts
10/10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning
no binaries found in the repo
Token-Permissions
0/10
Determines if the project's workflows follow the principle of least privilege.
Reasoning
detected GitHub workflow tokens with excessive permissions
CII-Best-Practices
0/10
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning
no effort to earn an OpenSSF best practices badge detected
Security-Policy
0/10
Determines if the project has published a security policy.
Reasoning
security policy file not detected
Fuzzing
0/10
Determines if the project uses fuzzing.
Reasoning
project is not fuzzed
License
10/10
Determines if the project has defined a license.
Reasoning
license file detected
Branch-Protection
0/10
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning
branch protection not enabled on development/release branches
Pinned-Dependencies
3/10
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning
dependency not pinned by hash detected -- score normalized to 3
Packaging
10/10
Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.
Reasoning
packaging workflow detected
SAST
0/10
Determines if the project uses static code analysis.
Reasoning
SAST tool is not run on all commits -- score normalized to 0

Project metadata as of .