Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-22 02:10 UTC

Tencent / tencent-goosefs-rust-sdk

Rust · PythonCustom license★ 1 star⑂ 1 forksince Jul 2026View on GitHub ↗

Tencent/tencent-goosefs-rust-sdk holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (68/100) and lowest on Security (34/100). It was last updated today. A single contributor accounts for most of its recent work.

54
overall / 100
Moderate

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.

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

Ownership

TencentOrganization
13,788 followers278 public repossince Apr 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iogoosefs-sdk0.1.858,02890 days agocachefilesystemgoosefsgrpcstoragenetwork-programming

Metrics by category

Vitality

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

59Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
0.7/36Commit cadence1/52 weeks with commits
6.3/18Commit volume4 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year4
human_commit_share
days_since_last_push0
active_weeks_last_year1
How it's scored
27/27Ships releases1 releases published
36/36Release recencylatest release 0 days ago
12.6/27Release cadencecadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count1
latest_release_tagv0.1.8
releases_from_tagsno
days_since_latest_release0
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
How it's scored
0/60Stars1 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
63.5/80Monthly downloads58,028 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesgoosefs-sdk
dependents
ecosystemscrates
total_downloads174,085
monthly_downloads58,028
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?

48Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
0/42Issue resolution0% of issues closed
0/30PR acceptance0/2 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/4 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues2
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0
closed_unmerged_prs2
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.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach13,788 followers of Tencent
25/25Track record278 public repos, account ~10 yr old
Inputs used
followers13,788
owner_typeOrganization
is_verified
owner_loginTencent
public_repos278
account_age_days3,750
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on crates
35/35Publish recencylatest publish 0 days ago
20/20Version history9 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgoosefs-sdk
ecosystemscrates
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/goosefs-sdk
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://docs.rs/goosefs-sdk
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

34At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/4 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): CI-Tests, 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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno 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.
How it's scored
12.6/18One-command bootstrapCargo.toml, bindings/python/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingbindings/python/python/goosefs/py.typed
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, uv.lock
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configsbindings/python/python/goosefs/py.typed
agent_commit_share
toolchain_manifestsCargo.toml, bindings/python/Cargo.toml
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeRust (statically typed)
52.5/55Manageable file sizes6/131 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes201,796
source_files_sampled131
oversized_source_files6
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)proto/grpc/block_worker.proto, proto/grpc/common.proto, proto/grpc/file_system_master.proto, proto/grpc/fscommon.proto, proto/grpc/metric_master.proto, proto/grpc/sasl/sasl_server.proto, proto/grpc/version.proto, proto/grpc/worker_manager_master.proto, proto/proto/dataserver/protocol.proto, proto/proto/dataserver/status.proto, proto/proto/security/capability_token.proto, proto/proto/security/token.proto, proto/proto/shared/acl.proto, proto/proto/shared/location.proto
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesproto/grpc/block_worker.proto, proto/grpc/common.proto, proto/grpc/file_system_master.proto, proto/grpc/fscommon.proto, proto/grpc/metric_master.proto, proto/grpc/sasl/sasl_server.proto, proto/grpc/version.proto, proto/grpc/worker_manager_master.proto, proto/proto/dataserver/protocol.proto, proto/proto/dataserver/status.proto, proto/proto/security/capability_token.proto, proto/proto/security/token.proto, proto/proto/shared/acl.proto, proto/proto/shared/location.proto
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

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

Data collection warnings

  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index crates:goosefs-sdk@0.1.8; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 3.4 / 10
3.4aggregate

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-22 02:10 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/4 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities11 existing vulnerabilities detected
Direct dependencies 23
RegistryPackageVersion constraintManifest
crates.iotonic0.14Cargo.toml
crates.iotonic-prost0.14Cargo.toml
crates.ioprost0.14.1Cargo.toml
crates.ioprost-types0.14.1Cargo.toml
crates.iotokio1.23Cargo.toml
crates.iotokio-stream0.1.14Cargo.toml
crates.iobytes1.11.1Cargo.toml
crates.iothiserror2Cargo.toml
crates.iotracing0.1Cargo.toml
crates.iodashmap6Cargo.toml
crates.ioitoa1Cargo.toml
crates.ioarc-swap1Cargo.toml
crates.ioxxhash-rust0.8.15Cargo.toml
crates.ioserde1Cargo.toml
crates.ioasync-trait0.1Cargo.toml
crates.iomemmap20.9Cargo.toml
crates.iolru0.12Cargo.toml
crates.iorand0.9.1Cargo.toml
crates.iouuid1.2Cargo.toml
crates.iohostname0.4Cargo.toml
crates.ioreqwest^0.12Cargo.toml
crates.iomoka0.12Cargo.toml
crates.iofutures0.3Cargo.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.

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

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