Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 06:14 UTC

spider-rs / chromey

Chrome DevTools Protocol for Rust

RustApache-2.0★ 51 stars⑂ 13 forkssince Jun 2025View on GitHub ↗
KindLibraryhow this is determined
#automation#chrome-devtools-protocol#headless-chrome#cdp

spider-rs/chromey holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (85/100) and lowest on Security (42/100). It was last updated today. A single contributor accounts for most of its recent work.

71
overall / 100
Good

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

71
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 63 is calibrated to 71 on the published index scale (record calibration 2026-08-02).

Ownership

spider-rsOrganization
106 followers66 public repossince Sep 2022

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iochromey2.54.014,1442380 days agoautomationcdpchromeplaywrightpuppeteerweb-programmingapi-bindings
crates.iospider_chromiumoxide_cdppoints to another repo — not scored0.7.940,6179136 days ago—
crates.iospider_chromiumoxide_fetcher0.8.1546113 days ago—
crates.iospider_chromiumoxide_pdlpoints to another repo — not scored0.7.640,6266136 days ago—
crates.iospider_chromiumoxide_typespoints to another repo — not scored0.7.640,720581 days ago—

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

85Excellent · 21% of overall

Development activity

86Excellent
How it's scored
36/36Push recency — last push 0 days ago
21.5/36Commit cadence — 31/52 weeks with commits
18/18Commit volume — 204 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year204
human_commit_share—
days_since_last_push0
active_weeks_last_year31

Release discipline

84Excellent
How it's scored
27/27Ships releases — 1 releases published
36/36Release recency — latest release 87 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv2.46.39
releases_from_tagsno
days_since_latest_release87
mean_days_between_releases—
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

50Moderate · 17% of overall

Popularity & adoption

37Weak
How it's scored
27.6/60Stars — 51 stars
9/25Forks — 13 forks
0/15Watchers — 0 watchers
Inputs used
forks13
stars51
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

69Good
How it's scored
55.4/80Monthly downloads — 14,198 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageschromey, spider_chromiumoxide_fetcher
dependents—
ecosystemscrates
total_downloads295,830
monthly_downloads14,198
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

65Good · 23% of overall

Maintainer resilience (bus factor)

21At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.4/22.5Commit distribution — top contributor authored 98% of commits
5.4/13.5Contributor breadth — 4 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.982

Issue & PR responsiveness

73Good
How it's scored
37.8/42Issue resolution — 90% of issues closed
25.7/30PR acceptance — 6/7 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs6
open_issues1
closed_issues9
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio0.9
closed_unmerged_prs1
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

82Excellent
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
14.6/25Owner reach — 106 followers of spider-rs
20.7/25Track record — 66 public repos, account ~3 yr old
Inputs used
followers106
owner_typeOrganization
is_verified—
owner_loginspider-rs
public_repos66
account_age_days1,409
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on crates
35/35Publish recency — latest publish 0 days ago
20/20Version history — 238 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageschromey, spider_chromiumoxide_fetcher
ecosystemscrates
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall

Engineering practices

68Good
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 3 out of 3 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

75Good
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://crates.io/crates/chromey
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsautomation, chrome-devtools-protocol, headless-chrome, cdp
has_wikiyes
homepagehttps://crates.io/crates/chromey
docs_sitehttps://crates.io/crates/chromey
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

42Weak · 16% of overall

Security posture

42Weak
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 3 out of 3 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

46Weak · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

40Weak
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share—
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.

Code legibility for models

98Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
52.5/55Manageable file sizes — 6/130 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes5,264,093
source_files_sampled130
oversized_source_files6

Machine-readable interfaces

100Exceptional
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

51GitHub stars
4contributors
204commits, last 12 months
0days since last push
1releases
1bus factor
1open issues
crates.iopackage ecosystems

Data collection warnings

  • crates package 'spider_chromiumoxide_cdp' points at a different repository (https://github.com/mattsse/chromiumoxide); excluded from ecosystem scoring
  • crates package 'spider_chromiumoxide_pdl' points at a different repository (https://github.com/mattsse/chromiumoxide); excluded from ecosystem scoring
  • crates package 'spider_chromiumoxide_types' points at a different repository (https://github.com/mattsse/chromiumoxide); excluded from ecosystem scoring
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.2 / 10
4.2aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-07-17 06:14 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests3 out of 3 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 66
RegistryPackageVersion constraintManifest
crates.iotokio-tungstenite0.29Cargo.toml
crates.ioserde1Cargo.toml
crates.iofutures-util0.3Cargo.toml
crates.ioserde_json1Cargo.toml
crates.iowhich8Cargo.toml
crates.iothiserror2Cargo.toml
crates.iourl2Cargo.toml
crates.iobase640.22Cargo.toml
crates.iofnv1Cargo.toml
crates.iotokio1Cargo.toml
crates.iotracing0.1Cargo.toml
crates.iopin-project-lite0.2Cargo.toml
crates.iodunce1Cargo.toml
crates.ioreqwest0.13Cargo.toml
crates.iolazy_static1Cargo.toml
crates.iophf0.13Cargo.toml
crates.ioadblock0.12Cargo.toml
crates.iorand0.10Cargo.toml
crates.iocase_insensitive_string0.2Cargo.toml
crates.iohashbrown0.16Cargo.toml
crates.ioaho-corasick1Cargo.toml
crates.iomemchr2Cargo.toml
crates.iosonic-rs0.5Cargo.toml
crates.iospider_network_blocker0Cargo.toml
crates.iospider_chromiumoxide_types0.7.6Cargo.toml
crates.iospider_chromiumoxide_cdp0.7Cargo.toml
crates.iospider_chromiumoxide_fetcher0.8Cargo.toml
crates.iohttp-cache-semantics3Cargo.toml
crates.iohttp-cache1.0.0-alpha.5Cargo.toml
crates.iohttp-cache-reqwest1.0.0-alpha.5Cargo.toml
crates.iohttp-global-cache0.2.0Cargo.toml
crates.iolol_html2Cargo.toml
crates.iotokio-stream0.1Cargo.toml
crates.ioauto_encoder0.1Cargo.toml
crates.ioserde_stacker0.1Cargo.toml
crates.ioblake31Cargo.toml
crates.iohex0.4Cargo.toml
crates.iodashmap6Cargo.toml
crates.iospider_remote_cache0.3Cargo.toml
crates.iospider_fingerprint2Cargo.toml
crates.iospider_firewall2Cargo.toml
crates.iospider_chromiumoxide_pdl0.7cdp/Cargo.toml
crates.iospider_chromiumoxide_types0.7cdp/Cargo.toml
crates.ioserde1cdp/Cargo.toml
crates.ioserde_json1cdp/Cargo.toml
crates.iothiserror2fetcher/Cargo.toml
crates.ioanyhow1fetcher/Cargo.toml
crates.iodirectories6fetcher/Cargo.toml
crates.ioserde1fetcher/Cargo.toml
crates.ioos_info3fetcher/Cargo.toml
crates.iozip8fetcher/Cargo.toml
crates.ioasync-std1.5fetcher/Cargo.toml
crates.iotokio1fetcher/Cargo.toml
crates.ioreqwest0.13fetcher/Cargo.toml
crates.iosurf2.3fetcher/Cargo.toml
crates.ioonce_cell1pdl/Cargo.toml
crates.ioregex1pdl/Cargo.toml
crates.ioquote1pdl/Cargo.toml
crates.ioproc-macro21pdl/Cargo.toml
crates.ioheck0.5pdl/Cargo.toml
crates.ioserde_json1pdl/Cargo.toml
crates.ioserde1pdl/Cargo.toml
crates.iospider_chromiumoxide_types0.7pdl/Cargo.toml
crates.ioeither1.15pdl/Cargo.toml
crates.ioserde1types/Cargo.toml
crates.ioserde_json1types/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Related records

Inspected repositories sharing catalogue tags or ecosystems with spider-rs/chromey. Read them side by side →

98apify/crawleeCrawlee—A web scraping and browser automation library for Node.js to build reliable crawlers. In JavaScript and TypeScript. Extract data for AI, LLMs, RAG, or GPTs. Download HTML, PDF, JPG, PNG, and other files from websites. Works with Puppeteer, Playwright, Cheerio, JSDOM, and raw HTTP. Both headful and headless mode. With proxy rotation.Exceptional90vercel-labs/agent-browserBrowser automation CLI for AI agentsExcellent99puppeteer/puppeteerJavaScript API for Chrome and FirefoxExceptional98apify/crawlee-pythonCrawlee—A web scraping and browser automation library for Python to build reliable crawlers. Extract data for AI, LLMs, RAG, or GPTs. Download HTML, PDF, JPG, PNG, and other files from websites. Works with Parsel, BeautifulSoup, Playwright, and raw HTTP. Both headful and headless mode. With proxy rotation.Exceptional91seleniumbase/SeleniumBase📊 APIs for web automation, testing, and bypassing bot-detection.Excellent90browser-use/browser-harnessBrowser Harness | Self-healing harness that enables LLMs to complete any task.Excellent

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — crates.io.