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

ai / check-dts

Unit tests for TypeScript definitions in your JS open source library

JavaScriptMIT★ 147 stars⑂ 10 forkssince Feb 2020View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

ai/check-dts holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Vitality (68/100) and lowest on AI Readiness (40/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

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)
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 59 is calibrated to 63 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 75% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

Andrey SitnikPersonal account
10,141 followers103 public repossince Aug 2008@evilmartians

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
npmcheck-dts2.0.116,4154045 days agochecktesttypestypescript

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
2.1/36Commit cadence — 3/52 weeks with commits
12.4/18Commit volume — 23 commits in the last year
8/10OpenSSF Scorecard: Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year23
human_commit_share1
days_since_last_push3
active_weeks_last_year3
How it's scored
27/27Ships releases — 7 releases published
36/36Release recency — latest release 45 days ago
12.6/27Release cadence — a release every ~133.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tag2.0.1
releases_from_tagsno
days_since_latest_release45
mean_days_between_releases133.3
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?

53Moderate · 17% of overall
How it's scored
35.1/60Stars — 147 stars
8/25Forks — 10 forks
2.7/15Watchers — 4 watchers
Inputs used
forks10
stars147
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
56.2/80Monthly downloads — 16,415 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescheck-dts
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads16,415
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.5/22.5Commit distribution — top contributor authored 93% of commits
13.5/13.5Contributor breadth — 14 contributors
10/10OpenSSF Scorecard: Contributors — project has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.932
How it's scored
39.2/42Issue resolution — 93% of issues closed
23.2/30PR acceptance — 24/31 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs24
open_issues1
closed_issues14
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.933
closed_unmerged_prs7
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
25/25Owner reach — 10,141 followers of ai
25/25Track record — 103 public repos, account ~18 yr old
Inputs used
followers10,141
owner_typeUser
is_verified—
owner_loginai
public_repos103
account_age_days6,616
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 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
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 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 — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 10 contributing companies or organizations
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
6/7.5Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 14 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.3
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier75
security_posture_after_multiplier40
security_posture_before_jurisdiction53
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 75% multiplier and gives Security posture an At risk ceiling of 34.

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_packages2
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:check-dts@2.0.1 runtime dependency closure — what installing the published package pulls in — 2 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.

40Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3.2/40Legible commit history — 6 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.06
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 — test/fixtures/tsconfig-override/tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstest/fixtures/tsconfig-override/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — JavaScript with type-check config (test/fixtures/tsconfig-override/tsconfig.json)
55/55Manageable file sizes — 0/46 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes6,421
source_files_sampled46
oversized_source_files0

Key facts

147GitHub stars
14contributors
23commits, last 12 months
3days since last push
7releases
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 ★ / 10 ⇿
0Stars
10Forks
4Releases

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.

02468101012020-022022-112025-08
Major 0Minor 2Patch 2

Each point covers 6 days.

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-14 04:18 UTC

10Binary-Artifactsno binaries found in the repo
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
10Contributorsproject has 10 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities14 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmnanospinner^1.2.2package.json
All dependencies 171

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

RegistryPackageVersionRelation
npmnanospinner1.2.2direct
npm@babel/helper-string-parser7.29.7indirect
npm@babel/helper-validator-identifier7.29.7indirect
npm@babel/parser7.29.7indirect
npm@babel/types7.29.7indirect
npm@bcoe/v8-coverage1.0.2indirect
npm@esbuild/aix-ppc640.27.4indirect
npm@esbuild/android-arm0.27.4indirect
npm@esbuild/android-arm640.27.4indirect
npm@esbuild/android-x640.27.4indirect
npm@esbuild/darwin-arm640.27.4indirect
npm@esbuild/darwin-x640.27.4indirect
npm@esbuild/freebsd-arm640.27.4indirect
npm@esbuild/freebsd-x640.27.4indirect
npm@esbuild/linux-arm0.27.4indirect
npm@esbuild/linux-arm640.27.4indirect
npm@esbuild/linux-ia320.27.4indirect
npm@esbuild/linux-loong640.27.4indirect
npm@esbuild/linux-mips64el0.27.4indirect
npm@esbuild/linux-ppc640.27.4indirect
npm@esbuild/linux-riscv640.27.4indirect
npm@esbuild/linux-s390x0.27.4indirect
npm@esbuild/linux-x640.27.4indirect
npm@esbuild/netbsd-arm640.27.4indirect
npm@esbuild/netbsd-x640.27.4indirect
npm@esbuild/openbsd-arm640.27.4indirect
npm@esbuild/openbsd-x640.27.4indirect
npm@esbuild/openharmony-arm640.27.4indirect
npm@esbuild/sunos-x640.27.4indirect
npm@esbuild/win32-arm640.27.4indirect
npm@esbuild/win32-ia320.27.4indirect
npm@esbuild/win32-x640.27.4indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@logux/oxc-configs1.0.0indirect
npm@oxlint-tsgolint/darwin-arm647.0.2001indirect
npm@oxlint-tsgolint/darwin-x647.0.2001indirect
npm@oxlint-tsgolint/linux-arm647.0.2001indirect
npm@oxlint-tsgolint/linux-x647.0.2001indirect
npm@oxlint-tsgolint/win32-arm647.0.2001indirect
npm@oxlint-tsgolint/win32-x647.0.2001indirect
npm@oxlint/binding-android-arm-eabi1.76.0indirect
npm@oxlint/binding-android-arm641.76.0indirect
npm@oxlint/binding-darwin-arm641.76.0indirect
npm@oxlint/binding-darwin-x641.76.0indirect
npm@oxlint/binding-freebsd-x641.76.0indirect
npm@oxlint/binding-linux-arm-gnueabihf1.76.0indirect
npm@oxlint/binding-linux-arm-musleabihf1.76.0indirect
npm@oxlint/binding-linux-arm64-gnu1.76.0indirect
npm@oxlint/binding-linux-arm64-musl1.76.0indirect
npm@oxlint/binding-linux-ppc64-gnu1.76.0indirect
npm@oxlint/binding-linux-riscv64-gnu1.76.0indirect
npm@oxlint/binding-linux-riscv64-musl1.76.0indirect
npm@oxlint/binding-linux-s390x-gnu1.76.0indirect
npm@oxlint/binding-linux-x64-gnu1.76.0indirect
npm@oxlint/binding-linux-x64-musl1.76.0indirect
npm@oxlint/binding-openharmony-arm641.76.0indirect
npm@oxlint/binding-win32-arm64-msvc1.76.0indirect
npm@oxlint/binding-win32-ia32-msvc1.76.0indirect
npm@oxlint/binding-win32-x64-msvc1.76.0indirect
npm@rollup/rollup-android-arm-eabi4.60.0indirect
npm@rollup/rollup-android-arm644.60.0indirect
npm@rollup/rollup-darwin-arm644.60.0indirect
npm@rollup/rollup-darwin-x644.60.0indirect
npm@rollup/rollup-freebsd-arm644.60.0indirect
npm@rollup/rollup-freebsd-x644.60.0indirect
npm@rollup/rollup-linux-arm-gnueabihf4.60.0indirect
npm@rollup/rollup-linux-arm-musleabihf4.60.0indirect
npm@rollup/rollup-linux-arm64-gnu4.60.0indirect
npm@rollup/rollup-linux-arm64-musl4.60.0indirect
npm@rollup/rollup-linux-loong64-gnu4.60.0indirect
npm@rollup/rollup-linux-loong64-musl4.60.0indirect
npm@rollup/rollup-linux-ppc64-gnu4.60.0indirect
npm@rollup/rollup-linux-ppc64-musl4.60.0indirect
npm@rollup/rollup-linux-riscv64-gnu4.60.0indirect
npm@rollup/rollup-linux-riscv64-musl4.60.0indirect
npm@rollup/rollup-linux-s390x-gnu4.60.0indirect
npm@rollup/rollup-linux-x64-gnu4.60.0indirect
npm@rollup/rollup-linux-x64-musl4.60.0indirect
npm@rollup/rollup-openbsd-x644.60.0indirect
npm@rollup/rollup-openharmony-arm644.60.0indirect
npm@rollup/rollup-win32-arm64-msvc4.60.0indirect
npm@rollup/rollup-win32-ia32-msvc4.60.0indirect
npm@rollup/rollup-win32-x64-gnu4.60.0indirect
npm@rollup/rollup-win32-x64-msvc4.60.0indirect
npm@standard-schema/spec1.1.0indirect
npm@types/chai5.2.3indirect
npm@types/deep-eql4.0.2indirect
npm@types/estree1.0.8indirect
npm@types/estree1.0.9indirect
npm@types/node22.13.14indirect
npm@typescript/typescript-aix-ppc647.0.2indirect
npm@typescript/typescript-darwin-arm647.0.2indirect
npm@typescript/typescript-darwin-x647.0.2indirect
npm@typescript/typescript-freebsd-arm647.0.2indirect
npm@typescript/typescript-freebsd-x647.0.2indirect
npm@typescript/typescript-linux-arm7.0.2indirect
npm@typescript/typescript-linux-arm647.0.2indirect
npm@typescript/typescript-linux-loong647.0.2indirect
npm@typescript/typescript-linux-mips64el7.0.2indirect
npm@typescript/typescript-linux-ppc647.0.2indirect
npm@typescript/typescript-linux-riscv647.0.2indirect
npm@typescript/typescript-linux-s390x7.0.2indirect
npm@typescript/typescript-linux-x647.0.2indirect
npm@typescript/typescript-netbsd-arm647.0.2indirect
npm@typescript/typescript-netbsd-x647.0.2indirect
npm@typescript/typescript-openbsd-arm647.0.2indirect
npm@typescript/typescript-openbsd-x647.0.2indirect
npm@typescript/typescript-sunos-x647.0.2indirect
npm@typescript/typescript-win32-arm647.0.2indirect
npm@typescript/typescript-win32-x647.0.2indirect
npm@vitest/coverage-v84.1.10indirect
npm@vitest/expect4.1.10indirect
npm@vitest/mocker4.1.10indirect
npm@vitest/pretty-format4.1.10indirect
npm@vitest/runner4.1.10indirect
npm@vitest/snapshot4.1.10indirect
npm@vitest/spy4.1.10indirect
npm@vitest/utils4.1.10indirect
npmactions-up1.16.0indirect
npmansi-colors4.1.3indirect
npmansi-regex5.0.1indirect
npmassertion-error2.0.1indirect
npmast-v8-to-istanbul1.0.5indirect
npmchai6.2.2indirect
npmconvert-source-map2.0.0indirect
npmenquirer2.4.1indirect
npmes-module-lexer2.3.1indirect
npmesbuild0.27.4indirect
npmeslint-plugin-prefer-let4.2.2indirect
npmestree-walker3.0.3indirect
npmexpect-type1.4.0indirect
npmfdir6.5.0indirect
npmfsevents2.3.3indirect
npmhas-flag4.0.0indirect
npmhtml-escaper2.0.2indirect
npmistanbul-lib-coverage3.2.2indirect
npmistanbul-lib-report3.0.1indirect
npmistanbul-reports3.2.0indirect
npmjs-tokens10.0.0indirect
npmmagic-string0.30.21indirect
npmmagicast0.5.3indirect
npmmake-dir4.0.0indirect
npmnanoid3.3.11indirect
npmobug2.1.4indirect
npmoxlint1.76.0indirect
npmoxlint-tsgolint7.0.2001indirect
npmpathe2.0.3indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.5indirect
npmpostcss8.5.8indirect
npmrequireindex1.2.0indirect
npmrollup4.60.0indirect
npmsemver7.8.5indirect
npmsiginfo2.0.0indirect
npmsource-map-js1.2.1indirect
npmstackback0.0.2indirect
npmstd-env4.2.0indirect
npmstrip-ansi6.0.1indirect
npmsupports-color7.2.0indirect
npmtinybench2.9.0indirect
npmtinyexec1.2.4indirect
npmtinyglobby0.2.17indirect
npmtinyrainbow3.1.1indirect
npmtypescript7.0.2indirect
npmundici-types6.20.0indirect
npmvite7.3.1indirect
npmvitest4.1.10indirect
npmwhy-is-node-running2.3.0indirect
npmyaml2.9.0indirect
Dependency advisories 0

Installing npm:check-dts@2.0.1 pulls in 2 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.