Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 13:43 UTC

aisk / rust-memcache

memcache client for rust

RustMIT★ 153 stars⑂ 45 forkssince Jul 2013View on GitHub ↗

aisk/rust-memcache holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Engineering Quality (84/100) and lowest on Security (33/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

75
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.

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

Ownership

An LongPersonal account
632 followers229 public repossince Mar 2011

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iomemcache0.21.0146,3754819 days agocachedatabasedrivermemcachememcached

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
5.5/36Commit cadence — 8/52 weeks with commits
16/18Commit volume — 59 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year59
human_commit_share0.97
days_since_last_push2
active_weeks_last_year8

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 2 releases published
36/36Release recency — latest release 19 days ago
27/27Release cadence — a release every ~34.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count2
latest_release_tagv0.21.0
releases_from_tagsno
days_since_latest_release19
mean_days_between_releases34.3

Community & Adoption

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

60Moderate · 17% of overall
How it's scored
35.4/60Stars — 153 stars
13.7/25Forks — 45 forks
3.9/15Watchers — 6 watchers
Inputs used
forks45
stars153
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
68.9/80Monthly downloads — 146,375 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesmemcache
dependents—
ecosystemscrates
total_downloads3,275,154
monthly_downloads146,375
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?

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.7/22.5Commit distribution — top contributor authored 88% of commits
13.5/13.5Contributor breadth — 17 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled17
top_contributor_share0.88
How it's scored
31.1/42Issue resolution — 74% of issues closed
27.7/30PR acceptance — 122/132 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs122
open_issues13
closed_issues37
prs_merged_7d11
prs_decided_7d11
prs_merged_30d12
prs_decided_30d13
issue_closed_ratio0.74
closed_unmerged_prs10
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
20.1/25Owner reach — 632 followers of aisk
25/25Track record — 229 public repos, account ~15 yr old
Inputs used
followers632
owner_typeUser
is_verified—
owner_loginaisk
public_repos229
account_age_days5,643
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on crates
35/35Publish recency — latest publish 19 days ago
20/20Version history — 48 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmemcache
ecosystemscrates
any_deprecatedno
min_days_since_publish19

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/memcache
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicsrust, rust-memcache, memcached, memcache, driver, client, cache
has_wikino
homepage—
docs_sitehttps://docs.rs/memcache
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

33At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestsCargo.toml
has_codeql_workflowno
has_security_policyno
has_dependabot_configyes
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

55Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
8.2/40Legible commit history — 15 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.155
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — rustfmt.toml
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 3 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.01
toolchain_manifestsCargo.toml
dependency_bot_commit_share0.03
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/36 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes56,507
source_files_sampled36
oversized_source_files0

Key facts

153GitHub stars
17contributors
59commits, last 12 months
2days since last push
2releases
1bus factor
13open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OSV advisory lookup failed: [Errno 101] Network is unreachable
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/aisk/rust-memcache: run: repo unreachable: Get "https://api.github.com/repos/aisk/rust-memcache": internal error: innerTransport.RoundTrip: internal error: innerTransport.RoundTrip: error in HTTP: net/http: TLS handshake timeout); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 45 ⇿
0Stars
45Forks

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.

010203040504522017-022021-082026-02

Each point covers 9 days.

Direct dependencies 11
RegistryPackageVersion constraintManifest
crates.iobyteorder1Cargo.toml
crates.iourl^2.1Cargo.toml
crates.iorand0.10Cargo.toml
crates.ioenum_dispatch0.3Cargo.toml
crates.iorustls0.23Cargo.toml
crates.iorustls-pki-types1Cargo.toml
crates.iorustls-native-certs0.8Cargo.toml
crates.ior2d2^0.8Cargo.toml
crates.iotokio1Cargo.toml
crates.ioserde1Cargo.toml
crates.ioserde_json1Cargo.toml
All dependencies 11

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

RegistryPackageVersionRelation
crates.iobyteorder—direct
crates.ioenum_dispatch—direct
crates.ior2d2—direct
crates.iorand—direct
crates.iorustls—direct
crates.iorustls-native-certs—direct
crates.iorustls-pki-types—direct
crates.ioserde—direct
crates.ioserde_json—direct
crates.iotokio—direct
crates.iourl—direct
Dependency advisories not assessed

Advisory matching could not run for this report: OSV advisory lookup failed: [Errno 101] Network is unreachable

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 statistics — crates.io.