Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-15 21:13 UTC

coder / claudecode.nvim

🧩 Claude Code Neovim IDE Extension

Lua · ShellMIT★ 3,000 stars⑂ 214 forkssince May 2025View on GitHub ↗

coder/claudecode.nvim holds a health index of 77 out of 100, placing it in the Good band. It scores highest on AI Readiness (76/100) and lowest on Security (58/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

CoderOrganization
2,619 followers234 public repossince Dec 2021

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

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
10.4/36Commit cadence15/52 weeks with commits
16.4/18Commit volume66 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year66
human_commit_share1
days_since_last_push4
active_weeks_last_year15
How it's scored
27/27Ships releases3 releases published
16.2/36Release recencylatest release 333 days ago
19.8/27Release cadencea release every ~52.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count3
latest_release_tagv0.3.0
releases_from_tagsno
days_since_latest_release333
mean_days_between_releases52.9
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?

74Good · 17% of overall
How it's scored
56.4/60Stars3,000 stars
19.4/25Forks214 forks
6.2/15Watchers14 watchers
Inputs used
forks214
stars3,000
watchers14
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.5/22.5Commit distributiontop contributor authored 80% of commits
13.5/13.5Contributor breadth26 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled26
top_contributor_share0.799
How it's scored
26.5/42Issue resolution63% of issues closed
22.9/30PR acceptance106/139 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 5/30 approved changesets -- score normalized to 1
Inputs used
merged_prs106
open_issues50
closed_issues85
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.63
closed_unmerged_prs33
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
24.6/25Owner reach2,619 followers of coder
22.4/25Track record234 public repos, account ~4 yr old
Inputs used
followers2,619
owner_typeOrganization
is_verified
owner_logincoder
public_repos234
account_age_days1,709
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicsclaude-code, neovim, claude
has_wikiyes
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?

58Moderate · 16% of overall
How it's scored
6.8/7.5Binary-Artifactsbinaries present in source code
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 5/30 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
3.8/7.5Vulnerabilities5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.8
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
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories5
affected_packages2
assessed_packages163
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 163 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

76Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.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, CLAUDE.md
agent_instruction_max_bytes23,293
How it's scored
18/18One-command bootstrapmise.toml
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentdevcontainer, lockfile
10/10Demonstrated agent practice33 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_filesmise.toml
has_devcontaineryes
has_linter_configno
typecheck_configs
agent_commit_share0.33
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeLua without a type-check config
55/55Manageable file sizes0/5 source files over 60KB
Inputs used
primary_languageLua
largest_source_bytes16,219
source_files_sampled5
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexample, sample
Inputs used
example_dirsexample, sample
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

3,000GitHub stars
26contributors
66commits, last 12 months
4days since last push
3releases
1bus factor
50open 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 ★ / 214 ⇿
0Stars
214Forks
3Releases

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.

0408012016020024021062025-052026-012026-08
Major 0Minor 3Patch 0

Each point covers 2 days.

OpenSSF Scorecard 4.8 / 10
4.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-15 21:13 UTC

9Binary-Artifactsbinaries present in source code
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
1Code-ReviewFound 5/30 approved changesets -- score normalized to 1
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
5Vulnerabilities5 existing vulnerabilities detected
All dependencies 163

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

RegistryPackageVersionRelation
npm@babel/code-frame7.29.7indirect
npm@babel/helper-validator-identifier7.29.7indirect
npm@conventional-commits/parser0.4.1indirect
npm@google-automations/git-file-utils3.0.1indirect
npm@iarna/toml3.0.0indirect
npm@jsep-plugin/assignment1.3.0indirect
npm@jsep-plugin/regex1.0.4indirect
npm@octokit/auth-token4.0.0indirect
npm@octokit/core5.2.2indirect
npm@octokit/endpoint9.0.6indirect
npm@octokit/graphql7.1.1indirect
npm@octokit/openapi-types24.2.0indirect
npm@octokit/plugin-paginate-rest11.4.4-cjs.2indirect
npm@octokit/plugin-request-log4.0.1indirect
npm@octokit/plugin-rest-endpoint-methods13.3.2-cjs.1indirect
npm@octokit/request8.4.1indirect
npm@octokit/request-error5.1.1indirect
npm@octokit/rest20.1.2indirect
npm@octokit/types13.10.0indirect
npm@types/minimist1.2.5indirect
npm@types/normalize-package-data2.4.4indirect
npm@types/npm-package-arg6.1.4indirect
npm@types/unist2.0.11indirect
npm@xmldom/xmldom0.8.13indirect
npmagent-base7.1.4indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmargparse2.0.1indirect
npmarray-ify1.0.0indirect
npmarrify1.0.1indirect
npmasync-retry1.3.3indirect
npmbalanced-match4.0.4indirect
npmbefore-after-hook2.2.3indirect
npmboolbase1.0.0indirect
npmbrace-expansion5.0.6indirect
npmcamelcase5.3.1indirect
npmcamelcase-keys6.2.2indirect
npmchalk4.1.2indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcompare-func2.0.0indirect
npmconventional-changelog-conventionalcommits6.1.0indirect
npmconventional-changelog-writer6.0.1indirect
npmconventional-commits-filter3.0.0indirect
npmcss-select5.2.2indirect
npmcss-what6.2.2indirect
npmdateformat3.0.3indirect
npmdebug4.4.3indirect
npmdecamelize1.2.0indirect
npmdecamelize-keys1.1.1indirect
npmdeprecation2.3.1indirect
npmdetect-indent6.1.0indirect
npmdiff8.0.4indirect
npmdom-serializer2.0.0indirect
npmdomelementtype2.3.0indirect
npmdomhandler5.0.3indirect
npmdomutils3.2.2indirect
npmdot-prop5.3.0indirect
npmemoji-regex8.0.0indirect
npmentities4.5.0indirect
npmerror-ex1.3.4indirect
npmes-errors1.3.0indirect
npmescalade3.2.0indirect
npmescape-string-regexp1.0.5indirect
npmfigures3.2.0indirect
npmfind-up4.1.0indirect
npmfunction-bind1.1.2indirect
npmget-caller-file2.0.5indirect
npmhandlebars4.7.9indirect
npmhard-rejection2.1.0indirect
npmhas-flag4.0.0indirect
npmhasown2.0.4indirect
npmhe1.2.0indirect
npmhosted-git-info2.8.9indirect
npmhosted-git-info4.1.0indirect
npmhttp-proxy-agent7.0.2indirect
npmhttps-proxy-agent7.0.6indirect
npmindent-string4.0.0indirect
npmis-arrayish0.2.1indirect
npmis-core-module2.16.2indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-obj2.0.0indirect
npmis-plain-obj1.1.0indirect
npmjs-tokens4.0.0indirect
npmjs-yaml4.2.0indirect
npmjsep1.4.0indirect
npmjson-parse-even-better-errors2.3.1indirect
npmjson-stringify-safe5.0.1indirect
npmjsonpath-plus10.4.0indirect
npmkind-of6.0.3indirect
npmlines-and-columns1.2.4indirect
npmlocate-path5.0.0indirect
npmlodash.ismatch4.4.0indirect
npmlru-cache6.0.0indirect
npmmap-obj1.0.1indirect
npmmap-obj4.3.0indirect
npmmeow8.1.2indirect
npmmin-indent1.0.1indirect
npmminimatch10.2.5indirect
npmminimist1.2.8indirect
npmminimist-options4.1.0indirect
npmmodify-values1.0.1indirect
npmms2.1.3indirect
npmneo-async2.6.2indirect
npmnode-html-parser6.1.13indirect
npmnormalize-package-data2.5.0indirect
npmnormalize-package-data3.0.3indirect
npmnth-check2.1.1indirect
npmonce1.4.0indirect
npmp-limit2.3.0indirect
npmp-locate4.1.0indirect
npmp-try2.2.0indirect
npmparse-github-repo-url1.4.1indirect
npmparse-json5.2.0indirect
npmpath-exists4.0.0indirect
npmpath-parse1.0.7indirect
npmpicocolors1.1.1indirect
npmprettier3.8.4indirect
npmquick-lru4.0.1indirect
npmread-pkg5.2.0indirect
npmread-pkg-up7.0.1indirect
npmredent3.0.0indirect
npmrelease-please17.9.0indirect
npmrequire-directory2.1.1indirect
npmresolve1.22.12indirect
npmretry0.13.1indirect
npmsemver5.7.2indirect
npmsemver7.8.4indirect
npmsource-map0.6.1indirect
npmspdx-correct3.2.0indirect
npmspdx-exceptions2.5.0indirect
npmspdx-expression-parse3.0.1indirect
npmspdx-license-ids3.0.23indirect
npmsplit1.0.1indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmstrip-indent3.0.0indirect
npmsupports-color7.2.0indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmthrough2.3.8indirect
npmtrim-newlines3.0.1indirect
npmtype-fest0.18.1indirect
npmtype-fest0.6.0indirect
npmtype-fest0.8.1indirect
npmtype-fest3.13.1indirect
npmtypescript4.9.5indirect
npmuglify-js3.19.3indirect
npmunist-util-is4.1.0indirect
npmunist-util-visit2.0.3indirect
npmunist-util-visit-parents3.1.1indirect
npmuniversal-user-agent6.0.1indirect
npmvalidate-npm-package-license3.0.4indirect
npmwordwrap1.0.0indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmxpath0.0.34indirect
npmy18n5.0.8indirect
npmyallist4.0.0indirect
npmyaml2.9.0indirect
npmyargs17.7.2indirect
npmyargs-parser20.2.9indirect
npmyargs-parser21.1.1indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 163 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion5.0.6indirecthigh35.0.9
js-yaml4.2.0indirecthigh24.3.1

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