Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-18 20:00 UTC

release-engineering / exodus-rsync

exodus-aware drop-in replacement for rsync

GoGPL-3.0★ 3 stars⑂ 12 forkssince Feb 2021View on GitHub ↗

release-engineering/exodus-rsync holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Vitality (83/100) and lowest on Community & Adoption (31/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

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.

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

Ownership

Red Hat Release EngineeringOrganization

80 followers104 public repossince Nov 2014

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
Go	github.com/release-engineering/exodus-rsync	v1.12.4	-	34	75 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall

Development activity

88Excellent

How it's scored

36/36	Push recency — last push 5 days ago
23.5/36	Commit cadence — 34/52 weeks with commits
18/18	Commit volume — 166 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	166
human_commit_share	0.54
days_since_last_push	5
active_weeks_last_year	34

Release discipline

76Good

How it's scored

27/27	Ships releases — 34 releases published
36/36	Release recency — latest release 75 days ago
12.6/27	Release cadence — a release every ~132.9 days
0/10	OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.

Inputs used

releases_count	34
latest_release_tag	v1.12.4
releases_from_tags	no
days_since_latest_release	75
mean_days_between_releases	132.9

Community & Adoption

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

31At Risk · 17% of overall

Popularity & adoption

15Critical

How it's scored

4.9/60	Stars — 3 stars
8.7/25	Forks — 12 forks
1.7/15	Watchers — 3 watchers

Inputs used

forks	12
stars	3
watchers	3
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 (GPL-3.0)
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	1
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	codecov.io
has_pull_request_template	no

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

67Good · 23% of overall

Maintainer resilience (bus factor)

33At Risk

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
3.4/22.5	Commit distribution — top contributor authored 85% of commits
10.8/13.5	Contributor breadth — 8 contributors
10/10	OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10

Inputs used

bus_factor	1
contributors_sampled	8
top_contributor_share	0.847

Issue & PR responsiveness

78Good

How it's scored

0/42	Issue resolution — no issues or no data
23.3/30	PR acceptance — 525/677 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — no data

Inputs used

merged_prs	525
open_issues	0
closed_issues	0
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	—
closed_unmerged_prs	152
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): Issue resolution, Newcomer PR acceptance, OpenSSF Scorecard: Code-Review. Remaining weights renormalized.

Ownership & stewardship

69Good

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
13.7/25	Owner reach — 80 followers of release-engineering
25/25	Track record — 104 public repos, account ~11 yr old

Inputs used

followers	80
owner_type	Organization
is_verified	no
owner_login	release-engineering
public_repos	104
account_age_days	4,364

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on go
35/35	Publish recency — latest publish 75 days ago
20/20	Version history — 34 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	github.com/release-engineering/exodus-rsync
ecosystems	go
any_deprecated	no
min_days_since_publish	75

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall

Engineering practices

68Good

How it's scored

24/24	CI workflows — 3 workflow(s)
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
20/20	OpenSSF Scorecard: CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

60Moderate

How it's scored

30/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
10/10	Topics — 2 topics
10/10	Wiki

Inputs used

topics	exodus-rsync, exodus
has_wiki	yes
homepage	—
docs_site	—
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?

69Good · 16% of overall

Security posture

61Moderate

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
2.5/2.5	CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — no data
2.5/2.5	Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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
7.5/7.5	Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
0/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5	SAST — SAST tool is run on all commits
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
6.8/7.5	Vulnerabilities — 1 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	15
scorecard_version	v5.5.0
checks_inconclusive	3
scorecard_aggregate	6.1

Excluded from scoring (no data or not applicable): Branch-Protection, Code-Review, Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	1
affected_packages	1
assessed_packages	34
unassessed_packages	0
affected_by_severity	unknown 1
direct_affected_packages	0

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 34 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

64Moderate · 4% of overall

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 — 53 of 54 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.981
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

69Good

How it's scored

18/18	One-command bootstrap — Makefile
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — Go (statically typed)
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
8/8	Automated maintenance — 46 of the last 100 commits are automated dependency updates
0/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0

Inputs used

has_nix	no
has_tests	yes
lockfiles	go.sum
has_dockerfile	no
typed_language	yes
bootstrap_files	Makefile
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	go.mod
dependency_bot_commit_share	0.46

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — Go (statically typed)
55/55	Manageable file sizes — 0/77 source files over 60KB

Inputs used

primary_language	Go
largest_source_bytes	32,161
source_files_sampled	77
oversized_source_files	0

Key facts

3GitHub stars

8contributors

166commits, last 12 months

5days since last push

34releases

1bus factor

0open issues

Gopackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 12 ⇿

0Stars

12Forks

33Releases

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 1Minor 14Patch 18

Each point covers 5 days.

OpenSSF Scorecard 6.1 / 10

6.1aggregate

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-10-18 20:00 UTC

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
10	CI-Tests	16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
n/a	Code-Review	Found no human activity in the last 16 changesets
10	Contributors	project has 3 contributing companies or organizations -- score normalized to 10
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
10	Maintained	30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
0	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 0
10	SAST	SAST tool is run on all commits
0	Security-Policy	security policy file not detected
0	Signed-Releases	Project has not signed or included provenance with any releases.
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
9	Vulnerabilities	1 existing vulnerabilities detected

Direct dependencies 15

Registry	Package	Version constraint	Manifest
Go	github.com/PuerkitoBio/rehttp	`v1.4.0`	go.mod
Go	github.com/adrg/xdg	`v0.5.3`	go.mod
Go	github.com/alecthomas/kong	`v1.16.1`	go.mod
Go	github.com/apex/log	`v1.9.0`	go.mod
Go	github.com/aws/aws-sdk-go-v2	`v1.47.2`	go.mod
Go	github.com/aws/aws-sdk-go-v2/credentials	`v1.20.6`	go.mod
Go	github.com/aws/aws-sdk-go-v2/feature/s3/transfermanager	`v0.4.13`	go.mod
Go	github.com/aws/aws-sdk-go-v2/service/s3	`v1.114.2`	go.mod
Go	github.com/aws/smithy-go	`v1.28.4`	go.mod
Go	github.com/coreos/go-systemd/v22	`v22.7.0`	go.mod
Go	github.com/gabriel-vasile/mimetype	`v1.4.15`	go.mod
Go	github.com/go-playground/validator/v10	`v10.30.3`	go.mod
Go	github.com/stretchr/testify	`v1.12.1`	go.mod
Go	go.uber.org/mock	`v0.6.0`	go.mod
Go	gopkg.in/yaml.v3	`v3.0.1`	go.mod

All dependencies 34

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

Registry	Package	Version	Relation
Go	github.com/adrg/xdg	`v0.5.3`	direct
Go	github.com/alecthomas/kong	`v1.16.1`	direct
Go	github.com/apex/log	`v1.9.0`	direct
Go	github.com/aws/aws-sdk-go-v2	`v1.47.2`	direct
Go	github.com/aws/aws-sdk-go-v2/credentials	`v1.20.6`	direct
Go	github.com/aws/aws-sdk-go-v2/feature/s3/transfermanager	`v0.4.13`	direct
Go	github.com/aws/aws-sdk-go-v2/service/s3	`v1.114.2`	direct
Go	github.com/aws/smithy-go	`v1.28.4`	direct
Go	github.com/coreos/go-systemd/v22	`v22.7.0`	direct
Go	github.com/gabriel-vasile/mimetype	`v1.4.15`	direct
Go	github.com/go-playground/validator/v10	`v10.30.3`	direct
Go	github.com/puerkitobio/rehttp	`v1.4.0`	direct
Go	github.com/stretchr/testify	`v1.12.1`	direct
Go	go.uber.org/mock	`v0.6.0`	direct
Go	gopkg.in/yaml.v3	`v3.0.1`	direct
Go	github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream	`v1.7.21`	indirect
Go	github.com/aws/aws-sdk-go-v2/internal/configsources	`v1.5.5`	indirect
Go	github.com/aws/aws-sdk-go-v2/internal/endpoints/v2	`v2.8.5`	indirect
Go	github.com/aws/aws-sdk-go-v2/internal/v4a	`v1.5.5`	indirect
Go	github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding	`v1.13.20`	indirect
Go	github.com/aws/aws-sdk-go-v2/service/internal/checksum	`v1.11.6`	indirect
Go	github.com/aws/aws-sdk-go-v2/service/internal/presigned-url	`v1.14.5`	indirect
Go	github.com/aws/aws-sdk-go-v2/service/internal/s3shared	`v1.20.5`	indirect
Go	github.com/fatih/color	`v1.19.0`	indirect
Go	github.com/go-playground/locales	`v0.14.2`	indirect
Go	github.com/go-playground/universal-translator	`v0.18.2`	indirect
Go	github.com/leodido/go-urn	`v1.4.0`	indirect
Go	github.com/mattn/go-colorable	`v0.1.15`	indirect
Go	github.com/mattn/go-isatty	`v0.0.24`	indirect
Go	github.com/pkg/errors	`v0.9.1`	indirect
Go	go.yaml.in/yaml/v3	`v3.0.5`	indirect
Go	golang.org/x/crypto	`v0.57.0`	indirect
Go	golang.org/x/sys	`v0.49.0`	indirect
Go	golang.org/x/text	`v0.42.0`	indirect

Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 34 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

Package	Version	Relation	Severity	Advisories	Fixed in
golang.org/x/crypto	`v0.57.0`	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 — Go.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records