Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-06 18:13 UTC

YawLabs / ctxlint

Lint your AI agent context files (CLAUDE.md, AGENTS.md, etc.) against your actual codebase

TypeScriptMIT★ 7 stars⑂ 3 forkssince Apr 2026View on GitHub ↗
KindCommand-line toolLibraryMCP serverhow this is determined

YawLabs/ctxlint holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (81/100) and lowest on Community & Adoption (48/100). It was last updated 11 days ago. A single contributor accounts for most of its recent work.

71
overall / 100
Good

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.

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

Ownership

Yaw LabsOrganization
9 followers28 public repossince Feb 2026

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

Package ecosystems

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
28.8/36Push recencylast push 11 days ago
11.1/36Commit cadence16/52 weeks with commits
18/18Commit volume202 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year202
human_commit_share0.84
days_since_last_push11
active_weeks_last_year16

Release discipline

100Exceptional
How it's scored
27/27Ships releases39 releases published
36/36Release recencylatest release 11 days ago
27/27Release cadencea release every ~5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count39
latest_release_tagv0.18.7
releases_from_tagsno
days_since_latest_release11
mean_days_between_releases5
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?

48Weak · 17% of overall
How it's scored
12.6/60Stars7 stars
2.5/25Forks3 forks
0/15Watchers1 watchers
Inputs used
forks3
stars7
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
57.7/80Monthly downloads21,412 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@yawlabs/ctxlint
dependents
ecosystemsnpm
total_downloads
monthly_downloads21,412
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?

59Moderate · 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
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution100% of issues closed
25.1/30PR acceptance41/49 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/17 approved changesets -- score normalized to 0
Inputs used
merged_prs41
open_issues0
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio1
closed_unmerged_prs8
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
7.2/25Owner reach9 followers of YawLabs
11.6/25Track record28 public repos, account ~0 yr old
Inputs used
followers9
owner_typeOrganization
is_verified
owner_loginYawLabs
public_repos28
account_age_days176
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 npm
35/35Publish recencylatest publish 11 days ago
20/20Version history57 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@yawlabs/ctxlint
ecosystemsnpm
any_deprecatedno
min_days_since_publish11

Engineering Quality

Are baseline engineering and documentation practices in place?

56Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests13 out of 25 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/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_diryes
has_descriptionyes

Security

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

64Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.2/2.5CI-Tests13 out of 25 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/17 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
3.5/5SASTSAST tool is not run on all commits -- score normalized to 7
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
0/7.5Vulnerabilities14 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.5
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages6
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:@yawlabs/ctxlint@0.18.7 runtime dependency closure — what installing the published package pulls in — 6 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.

77Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md, fixtures/bloated-claude-md/CLAUDE.md, fixtures/broken-paths/CLAUDE.md, fixtures/contradictions/AGENTS.md, fixtures/contradictions/CLAUDE.md, fixtures/diagram-and-prose/CLAUDE.md, fixtures/healthy-project/CLAUDE.md, fixtures/identical-redundancy/a/AGENTS.md, fixtures/identical-redundancy/b/AGENTS.md, fixtures/multiple-files/.cursorrules, fixtures/multiple-files/AGENTS.md, fixtures/multiple-files/CLAUDE.md, fixtures/nested-context/sub/CLAUDE.md, fixtures/redundant-content/CLAUDE.md, fixtures/wrong-commands/AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history64 of 84 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.762
agent_instruction_filesCLAUDE.md, fixtures/bloated-claude-md/CLAUDE.md, fixtures/broken-paths/CLAUDE.md, fixtures/contradictions/AGENTS.md, fixtures/contradictions/CLAUDE.md, fixtures/diagram-and-prose/CLAUDE.md, fixtures/healthy-project/CLAUDE.md, fixtures/identical-redundancy/a/AGENTS.md, fixtures/identical-redundancy/b/AGENTS.md, fixtures/multiple-files/.cursorrules, fixtures/multiple-files/AGENTS.md, fixtures/multiple-files/CLAUDE.md, fixtures/nested-context/sub/CLAUDE.md, fixtures/redundant-content/CLAUDE.md, fixtures/wrong-commands/AGENTS.md
agent_instruction_max_bytes4,838
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.js
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
10/10Demonstrated agent practice59 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance16 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.59
toolchain_manifests
dependency_bot_commit_share0.16
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/119 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes36,668
source_files_sampled119
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

7GitHub stars
1contributors
202commits, last 12 months
11days since last push
39releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

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

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-042026-052026-06
Major 0Minor 6Patch 25
OpenSSF Scorecard 5.5 / 10
5.5aggregate

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-06 18:12 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests13 out of 25 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/17 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
7SASTSAST tool is not run on all commits -- score normalized to 7
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
0Vulnerabilities14 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmpicomatch^4.0.4package.json
npmvscode-languageserver^10.0.0package.json
npmvscode-languageserver-textdocument^1.0.12package.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

Dependency advisories 0

Installing npm:@yawlabs/ctxlint@0.18.7 pulls in 6 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.31.0 — full methodology · metrics wiki.

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