Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 22:59 UTC

veeso / suppaftp

a super FTP/FTPS client library for Rust with full RFC support for both passive and active mode

RustApache-2.0★ 192 stars⑂ 48 forkssince Aug 2021View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

veeso/suppaftp holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Vitality (84/100) and lowest on Security (65/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

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

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

Ownership

Christian VisintinPersonal account
233 followers134 public repossince Apr 2017@holochain

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.iosuppaftp12.0.0299,840591 day agoasyncftpftp-clientftpsnetwork-protocolasynchronousnetwork-programming
crates.iosuppaftp-cli12.0.075321 day agoasyncftpftp-clientftpsnetwork-protocolasynchronousnetwork-programming

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
11.8/36Commit cadence — 17/52 weeks with commits
16.3/18Commit volume — 64 commits in the last year
10/10OpenSSF Scorecard: Maintained — 18 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year64
human_commit_share1
days_since_last_push1
active_weeks_last_year17

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 54 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~23.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count54
latest_release_tagv12.0.0
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases23.1
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?

77Good · 17% of overall
How it's scored
37/60Stars — 192 stars
13.9/25Forks — 48 forks
2.7/15Watchers — 4 watchers
Inputs used
forks48
stars192
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
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_badges8
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescoveralls.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
73/80Monthly downloads — 299,915 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessuppaftp, suppaftp-cli
dependents—
ecosystemscrates
total_downloads3,901,297
monthly_downloads299,915
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?

75Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.7/22.5Commit distribution — top contributor authored 44% of commits
13.5/13.5Contributor breadth — 38 contributors
10/10OpenSSF Scorecard: Contributors — project has 16 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled38
top_contributor_share0.436
How it's scored
37.6/42Issue resolution — 90% of issues closed
28.8/30PR acceptance — 94/98 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/24 approved changesets -- score normalized to 1
Inputs used
merged_prs94
open_issues8
closed_issues69
prs_merged_7d1
prs_decided_7d1
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.896
closed_unmerged_prs4
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
17/25Owner reach — 233 followers of veeso
25/25Track record — 134 public repos, account ~9 yr old
Inputs used
followers233
owner_typeUser
is_verified—
owner_loginveeso
public_repos134
account_age_days3,424
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 1 days ago
20/20Version history — 59 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessuppaftp, suppaftp-cli
ecosystemscrates
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
16/16Linter config — rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 20 out of 20 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/suppaftp/
10/10Repository description
10/10Topics — 11 topics
10/10Wiki
Inputs used
topicsftp, ftp-client, ftps, async, asynchronous, rust, rust-lang, rust-library, rust-crate, rust-ftp, async-ftp
has_wikiyes
homepage—
docs_sitehttps://docs.rs/suppaftp/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 20 out of 20 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.8/7.5Code-Review — Found 3/24 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 16 contributing companies or organizations
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 — 18 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
2.5/5SAST — SAST tool is not run on all commits -- score normalized to 5
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.5
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.

76Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes4,948
How it's scored
18/18One-command bootstrap — Justfile
0/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
0/8Automated maintenance — no automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_filesJustfile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.01
toolchain_manifestsCargo.toml, crates/suppaftp-cli/Cargo.toml, crates/suppaftp/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Rust (statically typed)
50.7/55Manageable file sizes — 3/38 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes94,491
source_files_sampled38
oversized_source_files3
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

192GitHub stars
38contributors
64commits, last 12 months
1days since last push
54releases
2bus factor
8open 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 ★ / 48 ⇿
0Stars
48Forks
50Releases

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.

010203040504822021-092024-032026-08
Major 6Minor 14Patch 30

Each point covers 5 days.

OpenSSF Scorecard 6.5 / 10
6.5aggregate

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-09 22:59 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests20 out of 20 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/24 approved changesets -- score normalized to 1
10Contributorsproject has 16 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained18 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
5SASTSAST tool is not run on all commits -- score normalized to 5
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 19
RegistryPackageVersion constraintManifest
crates.ioargh—crates/suppaftp-cli/Cargo.toml
crates.ioenv_logger—crates/suppaftp-cli/Cargo.toml
crates.iolog—crates/suppaftp-cli/Cargo.toml
crates.iorpassword—crates/suppaftp-cli/Cargo.toml
crates.iosuppaftp—crates/suppaftp-cli/Cargo.toml
crates.ioasync-native-tls-crate—crates/suppaftp/Cargo.toml
crates.ioasync-trait—crates/suppaftp/Cargo.toml
crates.iochrono—crates/suppaftp/Cargo.toml
crates.iofutures-rustls—crates/suppaftp/Cargo.toml
crates.iolazy-regex—crates/suppaftp/Cargo.toml
crates.iolog—crates/suppaftp/Cargo.toml
crates.ionative-tls-crate—crates/suppaftp/Cargo.toml
crates.iopin-project—crates/suppaftp/Cargo.toml
crates.iorustls-crate—crates/suppaftp/Cargo.toml
crates.iorustls-pki-types—crates/suppaftp/Cargo.toml
crates.iosmol—crates/suppaftp/Cargo.toml
crates.iothiserror—crates/suppaftp/Cargo.toml
crates.iotokio—crates/suppaftp/Cargo.toml
crates.iotokio-rustls-crate—crates/suppaftp/Cargo.toml
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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.