Public recordAt Risk
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 20:49 UTC
paritytech / jsonrpc
Rust JSON-RPC implementation
paritytech/jsonrpc holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (78/100) and lowest on Vitality (21/100). It was last updated 736 days ago. 2 contributors account for most of its recent work.
34
overall / 100Software 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.
34
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)
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 61 is calibrated to 67 on the published index scale (record calibration 2026-08-02).
Ownership
Parity TechnologiesOrganization · verified domain
2,065 followers777 public repossince Sep 2015
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| crates.io | jsonrpc-ws-server | 18.0.0 | 61,550 | 24 | 1864 days ago | — |
| crates.io | jsonrpc-ipc-server | 18.0.0 | 132,510 | 28 | 1864 days ago | — |
| crates.io | jsonrpc-tcp-server | 18.0.0 | 9,782 | 30 | 1864 days ago | — |
| crates.io | jsonrpc-core | 18.0.0 | 870,312 | 56 | 1864 days ago | jsonjson-rpcserderpcjsonrpcasynchronousnetwork-programming |
| crates.io | jsonrpc-http-server | 18.0.0 | 246,138 | 37 | 1864 days ago | jsonjson-rpcrpcjsonrpcserver |
| crates.io | jsonrpc-stdio-server | 18.0.0 | 9,489 | 24 | 1864 days ago | — |
| crates.io | jsonrpc-derive | 18.0.0 | 243,332 | 25 | 1864 days ago | — |
| crates.io | jsonrpc-pubsub | 18.0.0 | 213,704 | 29 | 1864 days ago | macrosjsonjson-rpcrpcjsonrpc |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
21
Development activity
1Critical
Abandonment alert
Work has arrived and nobody has attended to it
no human commit in 1036 daysautomated commits excludedpull requests left unansweredissues left unansweredreleases stalledOpenSSF Scorecard reports it unmaintainedcontinuous integration brokenOverall rating: At Risk ceiling
Silence alone is never the finding — a small, finished library may need no commits for years. This alert requires both: no human commit for a long time, and obligations the project is visibly not discharging. Automated commits do not count as maintenance.
How abandonment is assessedHow it's scored
| 0/36 | Push recency — last push 736 days ago |
| 0/36 | Commit cadence — 0/52 weeks with commits |
| 0/18 | Commit volume — 0 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
Inputs used
| commits_last_year | 0 |
| human_commit_share | 0.95 |
| days_since_last_push | 736 |
| active_weeks_last_year | 0 |
Release discipline
52Moderate
How it's scored
| 27/27 | Ships releases — 17 releases published |
| 0/36 | Release recency — latest release 1,907 days ago |
| 19.8/27 | Release cadence — a release every ~95.3 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 17 |
| latest_release_tag | v17.1.0 |
| releases_from_tags | no |
| days_since_latest_release | 1,907 |
| mean_days_between_releases | 95.3 |
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?
73
Popularity & adoption
77Good
How it's scored
| 47.2/60 | Stars — 818 stars |
| 20.2/25 | Forks — 264 forks |
| 9.4/15 | Watchers — 50 watchers |
Inputs used
| forks | 264 |
| stars | 818 |
| watchers | 50 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
50Moderate
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 0 |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | no |
Ecosystem adoption (downloads)
100Exceptional
How it's scored
| 80/80 | Monthly downloads — 1,786,817 downloads/month across crates |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | jsonrpc-ws-server, jsonrpc-ipc-server, jsonrpc-tcp-server, jsonrpc-core, jsonrpc-http-server, jsonrpc-stdio-server, jsonrpc-derive, jsonrpc-pubsub |
| dependents | — |
| ecosystems | crates |
| total_downloads | 47,678,653 |
| monthly_downloads | 1,786,817 |
| 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?
78
Maintainer resilience (bus factor)
63Moderate
How it's scored
| 25.2/54 | Bus factor — 2 contributor(s) cover half of all commits |
| 14.5/22.5 | Commit distribution — top contributor authored 36% of commits |
| 13.5/13.5 | Contributor breadth — 69 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 13 contributing companies or organizations |
Inputs used
| bus_factor | 2 |
| contributors_sampled | 69 |
| top_contributor_share | 0.355 |
Issue & PR responsiveness
82Excellent
How it's scored
| 30.4/42 | Issue resolution — 72% of issues closed |
| 26.3/30 | PR acceptance — 380/433 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 15/15 | OpenSSF Scorecard: Code-Review — all changesets reviewed |
Inputs used
| merged_prs | 380 |
| open_issues | 67 |
| closed_issues | 175 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | 0.723 |
| closed_unmerged_prs | 53 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
99Exceptional
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 20/20 | Verified domain |
| 23.8/25 | Owner reach — 2,065 followers of paritytech |
| 25/25 | Track record — 777 public repos, account ~10 yr old |
Inputs used
| followers | 2,065 |
| owner_type | Organization |
| is_verified | yes |
| owner_login | paritytech |
| public_repos | 777 |
| account_age_days | 4,006 |
Package maintenance
69Good
How it's scored
| 25/25 | Published & resolvable — 8 package(s) on crates |
| 4/35 | Publish recency — latest publish 1,864 days ago |
| 20/20 | Version history — 56 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | jsonrpc-ws-server, jsonrpc-ipc-server, jsonrpc-tcp-server, jsonrpc-core, jsonrpc-http-server, jsonrpc-stdio-server, jsonrpc-derive, jsonrpc-pubsub |
| ecosystems | crates |
| any_deprecated | no |
| min_days_since_publish | 1,864 |
Engineering Quality
Are baseline engineering and documentation practices in place?
68
Engineering practices
70Good
How it's scored
| 24/24 | CI workflows — 1 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — rustfmt.toml |
| 0/9.6 | Pre-commit hooks |
| 6.4/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | yes |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
65Good
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://docs.rs/jsonrpc-ws-server/ |
| 10/10 | Repository description |
| 0/10 | Topics |
| 10/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | yes |
| homepage | — |
| docs_site | https://docs.rs/jsonrpc-ws-server/ |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
67
Security posture
62Moderate
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 0/2.5 | CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 7.5/7.5 | Code-Review — all changesets reviewed |
| 2.5/2.5 | Contributors — project has 13 contributing companies or organizations |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 0/7.5 | Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — no data |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 5/5 | Security-Policy — security policy file detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 14 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 4 |
| scorecard_aggregate | 6.2 |
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Pinned-Dependencies, Signed-Releases. Remaining weights renormalized.
Dependency advisories
86Excellent
How it's scored
| 35/35 | Direct dependencies free of known advisories — no direct dependency carries a known advisory |
| 17.3/25 | Indirect dependencies free of known advisories — 3 affected: rand 0.7.3 (low), instant 0.1.13 (unknown), net2 0.2.39 (unknown) |
| 34/40 | No advisories left outstanding — 3 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,309 days ago |
Inputs used
| source | osv |
| advisories | 4 |
| affected_packages | 3 |
| assessed_packages | 103 |
| unassessed_packages | 0 |
| affected_by_severity | low 1, unknown 2 |
| direct_affected_packages | 0 |
Matched the crates:jsonrpc-ws-server@18.0.0 runtime dependency closure — what installing the published package pulls in — 103 packages. Reachability is not analyzed.
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.
62
Agent context & guidance
40Weak
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 95 of 95 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 1 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
How it's scored
| 12.6/18 | One-command bootstrap — Cargo.toml, core-client/Cargo.toml, core-client/transports/Cargo.toml (toolchain convention, no task runner) |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — rustfmt.toml |
| 11/11 | Static type checking — Rust (statically typed) |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 8/8 | Automated maintenance — 5 of the last 100 commits are automated dependency updates |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | — |
| agent_commit_share | 0 |
| toolchain_manifests | Cargo.toml, core-client/Cargo.toml, core-client/transports/Cargo.toml, core/Cargo.toml, derive/Cargo.toml, http/Cargo.toml, ipc/Cargo.toml, pubsub/Cargo.toml, pubsub/more-examples/Cargo.toml, server-utils/Cargo.toml, stdio/Cargo.toml, tcp/Cargo.toml, test/Cargo.toml, ws/Cargo.toml |
| dependency_bot_commit_share | 0.05 |
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
Code legibility for models
100Exceptional
How it's scored
| 45/45 | Type-checkable code — Rust (statically typed) |
| 55/55 | Manageable file sizes — 0/123 source files over 60KB |
Inputs used
| primary_language | Rust |
| largest_source_bytes | 34,651 |
| source_files_sampled | 123 |
| oversized_source_files | 0 |
How it's scored
| 0/40 | API schema (OpenAPI/GraphQL/proto) |
| 0/20 | MCP server |
| 40/40 | Runnable examples — examples |
Inputs used
| example_dirs | examples |
| has_mcp_signal | no |
| api_schema_files | — |
| interfaces_expected_of | network-service |
Key facts
818GitHub stars
69contributors
0commits, last 12 months
736days since last push
17releases
2bus factor
67open issues
crates.iopackage ecosystems
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
More detail
Star and fork history 0 ★ / 264 ⇿
0Stars
264Forks
17Releases
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.
Major 7Minor 4Patch 6
Each point covers 9 days.
OpenSSF Scorecard 6.2 / 10
6.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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| n/a | Branch-Protection | internal 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 |
| 0 | CI-Tests | 0 out of 30 merged PRs checked by a CI test -- score normalized to 0 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 10 | Code-Review | all changesets reviewed |
| 10 | Contributors | project has 13 contributing companies or organizations |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 0 | Maintained | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| n/a | Packaging | packaging workflow not detected |
| n/a | Pinned-Dependencies | no dependencies found |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 10 | Security-Policy | security policy file detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
Direct dependencies 62
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| crates.io | jsonrpc-client-transports | 18.0.0 | core-client/Cargo.toml |
| crates.io | futures | 0.3 | core-client/Cargo.toml |
| crates.io | log | 0.4 | core/Cargo.toml |
| crates.io | futures | 0.3 | core/Cargo.toml |
| crates.io | futures-util | 0.3 | core/Cargo.toml |
| crates.io | futures-executor | 0.3 | core/Cargo.toml |
| crates.io | serde | 1.0 | core/Cargo.toml |
| crates.io | serde_json | 1.0 | core/Cargo.toml |
| crates.io | serde_derive | 1.0 | core/Cargo.toml |
| crates.io | syn | 1.0 | derive/Cargo.toml |
| crates.io | proc-macro2 | 1.0 | derive/Cargo.toml |
| crates.io | quote | 1.0.6 | derive/Cargo.toml |
| crates.io | proc-macro-crate | 0.1.4 | derive/Cargo.toml |
| crates.io | futures | 0.3 | http/Cargo.toml |
| crates.io | hyper | 0.14 | http/Cargo.toml |
| crates.io | jsonrpc-core | 18.0.0 | http/Cargo.toml |
| crates.io | jsonrpc-server-utils | 18.0.0 | http/Cargo.toml |
| crates.io | log | 0.4 | http/Cargo.toml |
| crates.io | net2 | 0.2 | http/Cargo.toml |
| crates.io | parking_lot | 0.11.0 | http/Cargo.toml |
| crates.io | unicase | 2.0 | http/Cargo.toml |
| crates.io | futures | 0.3 | ipc/Cargo.toml |
| crates.io | log | 0.4 | ipc/Cargo.toml |
| crates.io | tower-service | 0.3 | ipc/Cargo.toml |
| crates.io | jsonrpc-core | 18.0.0 | ipc/Cargo.toml |
| crates.io | jsonrpc-server-utils | 18.0.0 | ipc/Cargo.toml |
| crates.io | parity-tokio-ipc | 0.9 | ipc/Cargo.toml |
| crates.io | parking_lot | 0.11.0 | ipc/Cargo.toml |
| crates.io | futures | 0.3 | pubsub/Cargo.toml |
| crates.io | jsonrpc-core | 18.0.0 | pubsub/Cargo.toml |
| crates.io | lazy_static | 1.4 | pubsub/Cargo.toml |
| crates.io | log | 0.4 | pubsub/Cargo.toml |
| crates.io | parking_lot | 0.11.0 | pubsub/Cargo.toml |
| crates.io | rand | 0.7 | pubsub/Cargo.toml |
| crates.io | serde | 1.0 | pubsub/Cargo.toml |
| crates.io | bytes | 1.0 | server-utils/Cargo.toml |
| crates.io | futures | 0.3 | server-utils/Cargo.toml |
| crates.io | globset | 0.4 | server-utils/Cargo.toml |
| crates.io | jsonrpc-core | 18.0.0 | server-utils/Cargo.toml |
| crates.io | lazy_static | 1.1.0 | server-utils/Cargo.toml |
| crates.io | log | 0.4 | server-utils/Cargo.toml |
| crates.io | tokio | 1 | server-utils/Cargo.toml |
| crates.io | tokio-util | 0.6 | server-utils/Cargo.toml |
| crates.io | tokio-stream | 0.1 | server-utils/Cargo.toml |
| crates.io | unicase | 2.0 | server-utils/Cargo.toml |
| crates.io | futures | 0.3 | stdio/Cargo.toml |
| crates.io | jsonrpc-core | 18.0.0 | stdio/Cargo.toml |
| crates.io | log | 0.4 | stdio/Cargo.toml |
| crates.io | tokio | 1 | stdio/Cargo.toml |
| crates.io | tokio-util | 0.6 | stdio/Cargo.toml |
| crates.io | jsonrpc-core | 18.0.0 | tcp/Cargo.toml |
| crates.io | jsonrpc-server-utils | 18.0.0 | tcp/Cargo.toml |
| crates.io | log | 0.4 | tcp/Cargo.toml |
| crates.io | parking_lot | 0.11.0 | tcp/Cargo.toml |
| crates.io | tower-service | 0.3 | tcp/Cargo.toml |
| crates.io | futures | 0.3 | ws/Cargo.toml |
| crates.io | jsonrpc-core | 18.0.0 | ws/Cargo.toml |
| crates.io | jsonrpc-server-utils | 18.0.0 | ws/Cargo.toml |
| crates.io | log | 0.4 | ws/Cargo.toml |
| crates.io | parking_lot | 0.11.0 | ws/Cargo.toml |
| crates.io | slab | 0.4 | ws/Cargo.toml |
| crates.io | parity-ws | 0.11.1 | ws/Cargo.toml |
All dependencies 42
Full resolved dependency set from the GitHub dependency graph: 29 direct and 13 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| crates.io | bytes | — | direct |
| crates.io | futures | — | direct |
| crates.io | futures-executor | — | direct |
| crates.io | futures-util | — | direct |
| crates.io | globset | — | direct |
| crates.io | hyper | — | direct |
| crates.io | jsonrpc-client-transports | — | direct |
| crates.io | jsonrpc-core | — | direct |
| crates.io | jsonrpc-server-utils | — | direct |
| crates.io | lazy_static | — | direct |
| crates.io | log | — | direct |
| crates.io | net2 | — | direct |
| crates.io | parity-tokio-ipc | — | direct |
| crates.io | parity-ws | — | direct |
| crates.io | parking_lot | — | direct |
| crates.io | proc-macro-crate | — | direct |
| crates.io | proc-macro2 | — | direct |
| crates.io | quote | — | direct |
| crates.io | rand | — | direct |
| crates.io | serde | — | direct |
| crates.io | serde_derive | — | direct |
| crates.io | serde_json | — | direct |
| crates.io | slab | — | direct |
| crates.io | syn | — | direct |
| crates.io | tokio | — | direct |
| crates.io | tokio-stream | — | direct |
| crates.io | tokio-util | — | direct |
| crates.io | tower-service | — | direct |
| crates.io | unicase | — | direct |
| crates.io | assert_matches | — | indirect |
| crates.io | derive_more | — | indirect |
| crates.io | env_logger | — | indirect |
| crates.io | hyper-tls | — | indirect |
| crates.io | jsonrpc-core-client | — | indirect |
| crates.io | jsonrpc-derive | — | indirect |
| crates.io | jsonrpc-http-server | — | indirect |
| crates.io | jsonrpc-ipc-server | — | indirect |
| crates.io | jsonrpc-pubsub | — | indirect |
| crates.io | jsonrpc-tcp-server | — | indirect |
| crates.io | jsonrpc-ws-server | — | indirect |
| crates.io | trybuild | — | indirect |
| crates.io | websocket | — | indirect |
Dependency advisories 3
Installing crates:jsonrpc-ws-server@18.0.0 pulls in 103 packages, direct and transitive: 3 carry known advisories, of which 0 are direct dependencies.
| Package | Version | Relation | Severity | Advisories | Fixed in |
|---|---|---|---|---|---|
| rand | 0.7.3 | indirect | low | 2 | 0.10.1 |
| instant | 0.1.13 | indirect | unknown | 1 | — |
| net2 | 0.2.39 | indirect | unknown | 1 | — |
An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.
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.
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 statistics — crates.io.