Public record
Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-07-28 13:39 UTC

xanzy / ssh-agent

Create a new SSH agent on any type of OS (so including Windows)

GoApache-2.0★ 64 stars⑂ 17 forkssince Dec 2015View on GitHub ↗

xanzy/ssh-agent holds a health index of 23 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (55/100) and lowest on Vitality (10/100). It was last updated 805 days ago. A single contributor accounts for most of its recent work.

23
overall / 100
At Risk

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.

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

Ownership

xanzyOrganization
14 followers6 public repossince Jul 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/xanzy/ssh-agentv0.3.3-71407 days ago

Metrics by category

Vitality

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

10Critical · 21% of overall
How it's scored
0/36Push recency — last push 805 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push805
active_weeks_last_year0
How it's scored
16.2/27Ships releases — 7 version tags (no GitHub releases)
0/36Release recency — latest release 1,407 days ago
5.4/27Release cadence — a release every ~411.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tagv0.3.3
releases_from_tagsyes
days_since_latest_release1,407
mean_days_between_releases411.8
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?

45Weak · 17% of overall
How it's scored
29.2/60Stars — 64 stars
10/25Forks — 17 forks
1.7/15Watchers — 3 watchers
Inputs used
forks17
stars64
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
11.2/22.5Commit distribution — top contributor authored 50% of commits
8.1/13.5Contributor breadth — 6 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.5
How it's scored
28/42Issue resolution — 67% of issues closed
24/30PR acceptance — 8/10 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 5/11 approved changesets -- score normalized to 4
Inputs used
merged_prs8
open_issues2
closed_issues4
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.667
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 backing — organization-owned
0/20Verified domain
8.5/25Owner reach — 14 followers of xanzy
18.2/25Track record — 6 public repos, account ~12 yr old
Inputs used
followers14
owner_typeOrganization
is_verified
owner_loginxanzy
public_repos6
account_age_days4,399
How it's scored
25/25Published & resolvable — 1 package(s) on go
4/35Publish recency — latest publish 1,407 days ago
20/20Version history — 7 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgithub.com/xanzy/ssh-agent
ecosystemsgo
any_deprecatedno
min_days_since_publish1,407

Engineering Quality

Are baseline engineering and documentation practices in place?

21At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 8 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

27At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 5/11 approved changesets -- score normalized to 4
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 21 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.1
Excluded from scoring (no data or not applicable): dangerous_workflow, packaging, pinned_dependencies, signed_releases, token_permissions. Remaining weights renormalized.
How it's scored
6.5/35Direct dependencies free of known advisories — 2 affected: golang.org/x/crypto 0.0.0-20220622213112-05595931fe9d (critical 10.0), golang.org/x/sys 0.0.0-20220715151400-c0bba94af5f8 (unknown)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
32/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 952 days ago
Inputs used
sourceosv
advisories39
affected_packages2
assessed_packages3
unassessed_packages0
affected_by_severitycritical 1, unknown 1
direct_affected_packages2
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 3 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.

45Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
29.3/40Legible commit history — 11 of 20 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.55
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrap — go.mod (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 20
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — Go (statically typed)
55/55Manageable file sizes — 0/3 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes4,281
source_files_sampled3
oversized_source_files0

Key facts

64GitHub stars
6contributors
0commits, last 12 months
805days since last push
7releases
1bus factor
2open 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 ★ / 17 ⇿
0Stars
17Forks
6Releases

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.

04812161622017-072021-092025-11
Major 0Minor 2Patch 4

Each point covers 8 days.

OpenSSF Scorecard 2.1 / 10
2.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-07-28 13:39 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 5/11 approved changesets -- score normalized to 4
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities21 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
Gogithub.com/Microsoft/go-winiov0.5.2go.mod
Gogolang.org/x/cryptov0.0.0-20220622213112-05595931fe9dgo.mod
Gogolang.org/x/sysv0.0.0-20220715151400-c0bba94af5f8go.mod
All dependencies 3

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

RegistryPackageVersionRelation
Gogithub.com/microsoft/go-winio0.5.2direct
Gogolang.org/x/crypto0.0.0-20220622213112-05595931fe9ddirect
Gogolang.org/x/sys0.0.0-20220715151400-c0bba94af5f8direct
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/crypto0.0.0-20220622213112-05595931fe9ddirectcritical383.4.0
golang.org/x/sys0.0.0-20220715151400-c0bba94af5f8directunknown10.44.0

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

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.5.0, schema v0.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsGo.