Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-06 02:46 UTC

servo / ipc-channel

A multiprocess drop-in replacement for Rust channels

RustApache-2.0★ 1,123 stars⑂ 159 forkssince Jun 2015View on GitHub ↗

servo/ipc-channel holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (84/100) and lowest on Security (47/100). It was last updated 4 days ago. 3 contributors account for most of its recent work.

83
overall / 100
Excellent

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.

83
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 70 is calibrated to 83 on the published index scale (record calibration 2026-08-02).

Ownership

ServoOrganization · verified domain
1,283 followers193 public repossince Oct 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.ioipc-channel0.23.0310,855424 days ago

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
10.4/36Commit cadence15/52 weeks with commits
12.9/18Commit volume26 commits in the last year
0/10OpenSSF Scorecard: Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year26
human_commit_share1
days_since_last_push4
active_weeks_last_year15
How it's scored
27/27Ships releases11 releases published
36/36Release recencylatest release 4 days ago
19.8/27Release cadencea release every ~91.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count11
latest_release_tagv0.23.0
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases91.4
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?

70Good · 17% of overall
How it's scored
49.5/60Stars1,123 stars
18.3/25Forks159 forks
7.2/15Watchers21 watchers
Inputs used
forks159
stars1,123
watchers21
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
73.2/80Monthly downloads310,855 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesipc-channel
dependents
ecosystemscrates
total_downloads6,072,075
monthly_downloads310,855
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?

84Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
13.9/22.5Commit distributiontop contributor authored 38% of commits
13.5/13.5Contributor breadth69 contributors
10/10OpenSSF Scorecard: Contributorsproject has 20 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled69
top_contributor_share0.381
How it's scored
24.1/42Issue resolution57% of issues closed
24.6/30PR acceptance255/311 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs255
open_issues57
closed_issues77
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.575
closed_unmerged_prs56
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
22.3/25Owner reach1,283 followers of servo
25/25Track record193 public repos, account ~13 yr old
Inputs used
followers1,283
owner_typeOrganization
is_verifiedyes
owner_loginservo
public_repos193
account_age_days5,073

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on crates
35/35Publish recencylatest publish 4 days ago
20/20Version history42 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesipc-channel
ecosystemscrates
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configrustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/ipc-channel
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://docs.rs/ipc-channel
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.2/2.5CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 20 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Branch-Protection, 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.

58Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history97 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.97
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format configrustfmt.toml
11/11Static type checkingRust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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_configyes
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
50/55Manageable file sizes2/22 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes1,302,797
source_files_sampled22
oversized_source_files2

Key facts

1,123GitHub stars
69contributors
26commits, last 12 months
4days since last push
11releases
3bus factor
57open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 159 ⇿
0Stars
159Forks
10Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

025507510012515015042015-072021-022026-09
Major 0Minor 5Patch 5

Each point covers 11 days.

OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-09-06 02:46 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
9CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 20 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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 8
RegistryPackageVersion constraintManifest
crates.iocrossbeam-channel0.5Cargo.toml
crates.iofutures-channel0.3.32Cargo.toml
crates.iofutures-core0.3.32Cargo.toml
crates.iolibc0.2.162Cargo.toml
crates.iopostcard1.1Cargo.toml
crates.ioserde_core1.0Cargo.toml
crates.iothiserror2.0.12Cargo.toml
crates.iouuid1Cargo.toml
All dependencies 18

Full resolved dependency set from the GitHub dependency graph: 8 direct and 10 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
crates.iocrossbeam-channeldirect
crates.iofutures-channeldirect
crates.iofutures-coredirect
crates.iolibcdirect
crates.iopostcarddirect
crates.ioserde_coredirect
crates.iothiserrordirect
crates.iouuiddirect
crates.iocriterionindirect
crates.iocrossbeam-utilsindirect
crates.iofutures-testindirect
crates.iomioindirect
crates.iorandindirect
crates.iorustc-hashindirect
crates.ioserdeindirect
crates.iostatic_assertionsindirect
crates.iotempfileindirect
crates.iowindowsindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.

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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.