Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 14:50 UTC

coder / agent-tty

Drive, inspect & record terminal sessions from the CLI

TypeScriptApache-2.0★ 29 stars⑂ 3 forkssince Mar 2026View on GitHub ↗
KindCommand-line toolLibraryTerminal interfacehow this is determined

coder/agent-tty holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on AI Readiness (81/100) and lowest on Community & Adoption (49/100). It was last updated 26 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

CoderOrganization · verified domain
2,786 followers241 public repossince Dec 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmagent-tty0.5.017510119 days agoterminaltuiautomationaitanstack-intent

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
28.8/36Push recency — last push 26 days ago
11.1/36Commit cadence — 16/52 weeks with commits
18/18Commit volume — 154 commits in the last year
5/10OpenSSF Scorecard: Maintained — 6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year154
human_commit_share0.78
days_since_last_push26
active_weeks_last_year16
How it's scored
27/27Ships releases — 10 releases published
27/36Release recency — latest release 119 days ago
27/27Release cadence — a release every ~8.2 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count10
latest_release_tagv0.5.0
releases_from_tagsno
days_since_latest_release119
mean_days_between_releases8.2

Community & Adoption

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

49Weak · 17% of overall
How it's scored
23.5/60Stars — 29 stars
2.5/25Forks — 3 forks
0/15Watchers — 0 watchers
Inputs used
forks3
stars29
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
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
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
29.9/80Monthly downloads — 175 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesagent-tty
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads175
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?

70Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.2/22.5Commit distribution — top contributor authored 99% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.992
How it's scored
40/42Issue resolution — 95% of issues closed
29/30PR acceptance — 148/153 decided PRs merged
6.5/13Newcomer PR acceptance — 1/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/26 approved changesets -- score normalized to 0
Inputs used
merged_prs148
open_issues1
closed_issues20
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d4
issue_closed_ratio0.952
closed_unmerged_prs5
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
24.8/25Owner reach — 2,786 followers of coder
22.7/25Track record — 241 public repos, account ~4 yr old
Inputs used
followers2,786
owner_typeOrganization
is_verifiedyes
owner_logincoder
public_repos241
account_age_days1,774

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 119 days ago
20/20Version history — 10 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesagent-tty
ecosystemsnpm
any_deprecatedno
min_days_since_publish119

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://github.com/coder/agent-tty/tree/main/docs
10/10Repository description
10/10Topics — 14 topics
0/10Wiki
Inputs used
topicsai-agents, automation, cli, developer-tools, ghostty, playwright, pty, recording, screenshots, terminal, testing, tui, claude-code, codex
has_wikino
homepagehttps://github.com/coder/agent-tty/tree/main/docs
docs_sitehttps://github.com/coder/agent-tty/tree/main/docs
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

66Good · 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 — 30 out of 30 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/7.5Code-Review — Found 1/26 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
3.8/7.5Maintained — 6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5.8

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages50
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:agent-tty@0.5.0 runtime dependency closure — what installing the published package pulls in — 50 packages. 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.

81Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 78 of 78 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes11,803
How it's scored
18/18One-command bootstrap — mise.toml
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
0/10Reproducible environment
10/10Demonstrated agent practice — 26 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_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_filesmise.toml
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0.26
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/373 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes58,949
source_files_sampled373
oversized_source_files0

Key facts

29GitHub stars
2contributors
154commits, last 12 months
26days since last push
10releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

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

More detail

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

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.

12233312026-072026-072026-08
OpenSSF Scorecard 5.8 / 10
5.8aggregate

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-20 14:50 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/26 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
npmcommander14.0.3package.json
npmghostty-web0.4.0package.json
npmink^7.0.5package.json
npmnode-pty1.1.0package.json
npmplaywright1.60.0package.json
npmreact^19.2.7package.json
npmulid3.0.2package.json
npmzod4.3.6package.json
All dependencies 19

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

RegistryPackageVersionRelation
npmcommander14.0.3direct
npmghostty-web0.4.0direct
npmink^7.0.5direct
npmnode-pty1.1.0direct
npmplaywright1.60.0direct
npmreact^19.2.7direct
npmulid3.0.2direct
npmzod4.3.6direct
npm@coder/libghostty-vt-node0.1.0-beta.0indirect
npm@types/node25.5.0indirect
npm@types/react^19.2.16indirect
npmoxfmt0.47.0indirect
npmoxlint1.62.0indirect
npmoxlint-tsgolint0.22.1indirect
npmrelease-please17.9.0indirect
npmrimraf6.1.3indirect
npmtsx4.21.0indirect
npmtypescript5.9.3indirect
npmvitest4.1.11indirect
Dependency advisories 0

Installing npm:agent-tty@0.5.0 pulls in 50 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.

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 — npm.