Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 17:14 UTC

dsherret / ts-morph

TypeScript Compiler API wrapper for static analysis and programmatic code changes.

TypeScriptMIT★ 6,181 stars⑂ 238 forkssince Mar 2017View on GitHub ↗

dsherret/ts-morph holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (90/100) and lowest on AI Readiness (47/100). It was last updated 8 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

David SherretPersonal account
2,126 followers180 public repossince Apr 2012

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
npm@ts-morph/common0.29.099,426,17848157 days ago—
npmts-morph28.0.093,602,87789157 days agotypescriptaststatic-analysiscode-generationcode-refactor
npm@ts-morph/bootstrap0.29.0482,93338157 days agotypescriptcompilerbootstrap

Metrics by category

Vitality

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

59Moderate · 21% of overall
How it's scored
28.8/36Push recency — last push 8 days ago
2.1/36Commit cadence — 3/52 weeks with commits
9.4/18Commit volume — 10 commits in the last year
4/10OpenSSF Scorecard: Maintained — 1 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year10
human_commit_share1
days_since_last_push8
active_weeks_last_year3
How it's scored
27/27Ships releases — 24 releases published
27/36Release recency — latest release 157 days ago
19.8/27Release cadence — a release every ~84.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count24
latest_release_tag28.0.0
releases_from_tagsno
days_since_latest_release157
mean_days_between_releases84.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?

90Excellent · 17% of overall
How it's scored
60/60Stars — 6,181 stars
19.8/25Forks — 238 forks
7/15Watchers — 19 watchers
Inputs used
forks238
stars6,181
watchers19
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 (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 193,511,988 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@ts-morph/common, ts-morph, @ts-morph/bootstrap
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads193,511,988
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?

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.1/22.5Commit distribution — top contributor authored 95% of commits
13.5/13.5Contributor breadth — 64 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled64
top_contributor_share0.951
How it's scored
32.7/42Issue resolution — 78% of issues closed
26.9/30PR acceptance — 200/223 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 8/30 approved changesets -- score normalized to 2
Inputs used
merged_prs200
open_issues281
closed_issues988
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.779
closed_unmerged_prs23
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
23.9/25Owner reach — 2,126 followers of dsherret
25/25Track record — 180 public repos, account ~14 yr old
Inputs used
followers2,126
owner_typeUser
is_verified—
owner_logindsherret
public_repos180
account_age_days5,280
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 3 package(s) on npm
35/35Publish recency — latest publish 157 days ago
20/20Version history — 89 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@ts-morph/common, ts-morph, @ts-morph/bootstrap
ecosystemsnpm
any_deprecatedno
min_days_since_publish157

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 16 out of 30 merged PRs checked by a CI test -- score normalized to 5
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://ts-morph.com
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicstypescript, ast, code-generation, javascript, static-analysis
has_wikino
homepagehttps://ts-morph.com
docs_sitehttps://ts-morph.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

59Moderate · 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
1.2/2.5CI-Tests — 16 out of 30 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 8/30 approved changesets -- score normalized to 2
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/7.5Maintained — 1 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 4
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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 — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

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_packages9
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:ts-morph@28.0.0 runtime dependency closure — what installing the published package pulls in — 9 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.

47Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 98 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.98
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — packages/bootstrap/tsconfig.json, packages/common/tsconfig.json, packages/ts-morph/tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configspackages/bootstrap/tsconfig.json, packages/common/tsconfig.json, packages/ts-morph/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.6/55Manageable file sizes — 9/1,175 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes2,899,153
source_files_sampled1,175
oversized_source_files9

Key facts

6,181GitHub stars
64contributors
10commits, last 12 months
8days since last push
24releases
1bus factor
281open issues
npm, RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 238 ⇿
0Stars
238Forks
24Releases

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.

0408012016020024023642017-062022-012026-09
Major 16Minor 2Patch 6

Each point covers 9 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-17 17:14 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
5CI-Tests16 out of 30 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 8/30 approved changesets -- score normalized to 2
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
4Maintained1 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 4
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
npm@ts-morph/common~0.29.0packages/bootstrap/package.json
npmminimatch^10.0.1packages/common/package.json
npmpath-browserify^1.0.1packages/common/package.json
npmtinyglobby^0.2.14packages/common/package.json
npm@ts-morph/common~0.29.0packages/ts-morph/package.json
npmcode-block-writer^13.0.3packages/ts-morph/package.json
All dependencies 25

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

RegistryPackageVersionRelation
npm@ts-morph/common~0.29.0direct
npmcode-block-writer^13.0.3direct
npmminimatch^10.0.1direct
npmpath-browserify^1.0.1direct
npmtinyglobby^0.2.14direct
npm@rollup/plugin-typescript^12.1.2indirect
npm@types/chai^5.2.1indirect
npm@types/diff^7.0.2indirect
npm@types/mocha^10.0.10indirect
npm@types/node^22.14.1indirect
npmchai^5.2.0indirect
npmconditional-type-checks^1.0.6indirect
npmcross-env^7.0.3indirect
npmdiff^7.0.0indirect
npmdprint^0.50.1indirect
npmmocha11.1.0indirect
npmmocha^11.1.0indirect
npmrimraf^6.0.1indirect
npmrollup4.40.0indirect
npmts-node10.9.2indirect
npmts-node^10.9.2indirect
npmtslib^2.8.1indirect
npmtypescript6.0.2indirect
npmtypescript~6.0.2indirect
RubyGemsgithub-pages—indirect
Dependency advisories 0

Installing npm:ts-morph@28.0.0 pulls in 9 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.