Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-03 15:04 UTC

Dicklesworthstone / ntm

Named Tmux Manager: spawn, tile, and coordinate multiple AI coding agents (Claude, Codex, Gemini) across tmux panes with a TUI command palette

GoCustom license★ 411 stars⑂ 61 forkssince Dec 2025View on GitHub ↗
KindWeb interfaceCommand-line toolTerminal interfacehow this is determined

Dicklesworthstone/ntm holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on AI Readiness (94/100) and lowest on Sustainability & Governance (52/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Jeff EmanuelPersonal account
3,075 followers194 public repossince Jan 2018

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 publish
Gogithub.com/Dicklesworthstone/ntmv1.20.0-3212 days ago

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
23.5/36Commit cadence34/52 weeks with commits
18/18Commit volume3,934 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year3,934
human_commit_share1
days_since_last_push0
active_weeks_last_year34

Release discipline

94Exceptional
How it's scored
27/27Ships releases30 releases published
36/36Release recencylatest release 12 days ago
27/27Release cadencea release every ~7 days
4/10OpenSSF Scorecard: Signed-Releases3 out of the last 5 releases have a total of 3 signed artifacts.
Inputs used
releases_count30
latest_release_tagv1.20.0
releases_from_tagsno
days_since_latest_release12
mean_days_between_releases7

Community & Adoption

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

60Moderate · 17% of overall
How it's scored
42.4/60Stars411 stars
14.8/25Forks61 forks
0/15Watchers2 watchers
Inputs used
forks61
stars411
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/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_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

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

52Moderate · 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
40/42Issue resolution95% of issues closed
0/30PR acceptance0/30 decided PRs merged
0/13Newcomer PR acceptance0/5 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues10
closed_issues200
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d5
issue_closed_ratio0.952
closed_unmerged_prs30
first_time_authors_30d4
first_time_prs_merged_30d0
first_time_prs_decided_30d5
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
25/25Owner reach3,075 followers of Dicklesworthstone
25/25Track record194 public repos, account ~8 yr old
Inputs used
followers3,075
owner_typeUser
is_verified
owner_loginDicklesworthstone
public_repos194
account_age_days3,134
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 go
35/35Publish recencylatest publish 12 days ago
20/20Version history32 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/Dicklesworthstone/ntm
ecosystemsgo
any_deprecatedno
min_days_since_publish12

Engineering Quality

Are baseline engineering and documentation practices in place?

82Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.golangci.yml, eslint.config.mjs
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_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicsai-agents, cli, developer-tools, go, tmux
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
6.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/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/30 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
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
5/5Pinned-Dependenciesall dependencies are pinned
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
3/7.5Signed-Releases3 out of the last 5 releases have a total of 3 signed artifacts.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities36 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): CI-Tests. 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.

94Exceptional · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 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_filesAGENTS.md
agent_instruction_max_bytes38,091
How it's scored
18/18One-command bootstrapMakefile, third_party/bubbletea/Taskfile.yaml
22/22Automated tests
11/11Lint / format config.golangci.yml, eslint.config.mjs
11/11Static type checkingvscode/tsconfig.json, web/tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
10/10Demonstrated agent practice68 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum, package-lock.json
has_dockerfileyes
typed_languageyes
bootstrap_filesMakefile, third_party/bubbletea/Taskfile.yaml
has_devcontainerno
has_linter_configyes
typecheck_configsvscode/tsconfig.json, web/tsconfig.json
agent_commit_share0.68
toolchain_manifestsgo.mod, internal/ensemble/testdata/context/full-project/go.mod, third_party/bubbletea/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeGo (statically typed)
53/55Manageable file sizes66/1,845 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes495,538
source_files_sampled1,845
oversized_source_files66
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)docs/openapi.json
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesdocs/openapi.json
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

411GitHub stars
1contributors
3,934commits, last 12 months
0days since last push
30releases
1bus factor
10open issues
Go, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'ntm-vscode' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 61 ⇿
0Stars
61Forks
28Releases

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.

013253850636132025-122026-042026-07
Major 0Minor 17Patch 11
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-08-03 15:04 UTC

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
4Signed-Releases3 out of the last 5 releases have a total of 3 signed artifacts.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities36 existing vulnerabilities detected
Direct dependencies 31
RegistryPackageVersion constraintManifest
Gogithub.com/BurntSushi/tomlv1.6.0go.mod
Gogithub.com/charmbracelet/bubblesv1.0.0go.mod
Gogithub.com/charmbracelet/bubbleteav1.3.10go.mod
Gogithub.com/charmbracelet/glamourv1.0.0go.mod
Gogithub.com/charmbracelet/harmonicav0.2.0go.mod
Gogithub.com/charmbracelet/huhv1.0.0go.mod
Gogithub.com/charmbracelet/lipglossv1.1.1-0.20250404203927-76690c660834go.mod
Gogithub.com/charmbracelet/x/ansiv0.11.7go.mod
Gogithub.com/chromedp/cdprotov0.0.0-20260427013145-5737772c319bgo.mod
Gogithub.com/chromedp/chromedpv0.15.1go.mod
Gogithub.com/fsnotify/fsnotifyv1.10.1go.mod
Gogithub.com/go-chi/chi/v5v5.2.5go.mod
Gogithub.com/gorilla/websocketv1.5.3go.mod
Gogithub.com/mattn/go-isattyv0.0.22go.mod
Gogithub.com/mattn/go-runewidthv0.0.23go.mod
Gogithub.com/muesli/reflowv0.3.0go.mod
Gogithub.com/muesli/termenvv0.16.0go.mod
Gogithub.com/sergi/go-diffv1.4.0go.mod
Gogithub.com/shirou/gopsutil/v4v4.26.4go.mod
Gogithub.com/spf13/cobrav1.10.2go.mod
Gogithub.com/spf13/pflagv1.0.10go.mod
Gogolang.org/x/sysv0.44.0go.mod
Gogolang.org/x/termv0.43.0go.mod
Gogopkg.in/yaml.v3v3.0.1go.mod
Gomodernc.org/sqlitev1.50.1go.mod
npm@tanstack/react-query^5.100.10web/package.json
npmnext^16.2.6web/package.json
npmopenapi-fetch^0.17.0web/package.json
npmreact^19.2.6web/package.json
npmreact-dom^19.2.6web/package.json
npmzod^4.4.3web/package.json
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.30.0 — full methodology · metrics wiki.

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