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

neoclide / coc-yaml

Yaml language server extension for coc.nvim

TypeScriptMIT★ 245 stars⑂ 24 forkssince Nov 2018View on GitHub ↗
KindLibraryhow this is determined
#yaml#vim#neovim

neoclide/coc-yaml holds a health index of 60 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (65/100) and lowest on AI Readiness (47/100). It was last updated 38 days ago. A single contributor accounts for most of its recent work.

60
overall / 100
Moderate

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.

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

Ownership

NeoclideOrganization
232 followers73 public repossince Nov 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmcoc-yaml1.9.38,9203038 days agococ.nvimyaml

Metrics by category

Vitality

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

50Moderate · 21% of overall

Development activity

36Weak
How it's scored
18/36Push recency — last push 38 days ago
0.7/36Commit cadence — 1/52 weeks with commits
7.6/18Commit volume — 6 commits in the last year
10/10OpenSSF Scorecard: Maintained — 6 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year6
human_commit_share0.976
days_since_last_push38
active_weeks_last_year1

Release discipline

72Good
How it's scored
16.2/27Ships releases — 29 version tags (no GitHub releases)
36/36Release recency — latest release 38 days ago
12.6/27Release cadence — a release every ~181.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count29
latest_release_tag1.9.3
releases_from_tagsyes
days_since_latest_release38
mean_days_between_releases181.1
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?

55Moderate · 17% of overall

Popularity & adoption

53Moderate
How it's scored
38.7/60Stars — 245 stars
11.3/25Forks — 24 forks
2.7/15Watchers — 4 watchers
Inputs used
forks24
stars245
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

50Moderate
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_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

66Good
How it's scored
52.7/80Monthly downloads — 8,920 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescoc-yaml
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads8,920
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?

65Good · 23% of overall

Maintainer resilience (bus factor)

32At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.1/22.5Commit distribution — top contributor authored 86% of commits
13.5/13.5Contributor breadth — 12 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.863

Issue & PR responsiveness

71Good
How it's scored
41.3/42Issue resolution — 98% of issues closed
18.8/30PR acceptance — 15/24 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 3/30 approved changesets -- score normalized to 1
Inputs used
merged_prs15
open_issues1
closed_issues58
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.983
closed_unmerged_prs9
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.

Ownership & stewardship

72Good
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
17/25Owner reach — 232 followers of neoclide
25/25Track record — 73 public repos, account ~9 yr old
Inputs used
followers232
owner_typeOrganization
is_verifiedno
owner_loginneoclide
public_repos73
account_age_days3,586

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

53Moderate · 19% of overall

Engineering practices

48Weak
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
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/10Topics — 3 topics
10/10Wiki
Inputs used
topicsyaml, vim, neovim
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?

62Moderate · 16% of overall

Security posture

52Moderate
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 3/30 approved changesets -- score normalized to 1
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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
7.5/7.5Maintained — 6 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.2
Excluded from scoring (no data or not applicable): Packaging, 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_packages1
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:coc-yaml@1.9.3 runtime dependency closure — what installing the published package pulls in — 1 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

Agent context & guidance

11Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
11.1/40Legible commit history — 17 of 82 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.207
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

54Moderate
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 84
8/8Automated maintenance — 2 of the last 84 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.024

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/20 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes12,201
source_files_sampled20
oversized_source_files0

Key facts

245GitHub stars
12contributors
6commits, last 12 months
38days since last push
29releases
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 ★ / 24 ⇿
0Stars
24Forks
25Releases

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.

048121620242322019-112022-112025-11
Major 0Minor 9Patch 16

Each point covers 6 days.

OpenSSF Scorecard 5.2 / 10
5.2aggregate

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-15 17:09 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/30 approved changesets -- score normalized to 1
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained6 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
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 1
RegistryPackageVersion constraintManifest
npmprettier2.0.5package.json
All dependencies 75

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

RegistryPackageVersionRelation
npmprettier2.0.5direct
npm@chemzqm/tsconfig0.0.3indirect
npm@esbuild/aix-ppc640.25.0indirect
npm@esbuild/android-arm0.25.0indirect
npm@esbuild/android-arm640.25.0indirect
npm@esbuild/android-x640.25.0indirect
npm@esbuild/darwin-arm640.25.0indirect
npm@esbuild/darwin-x640.25.0indirect
npm@esbuild/freebsd-arm640.25.0indirect
npm@esbuild/freebsd-x640.25.0indirect
npm@esbuild/linux-arm0.25.0indirect
npm@esbuild/linux-arm640.25.0indirect
npm@esbuild/linux-ia320.25.0indirect
npm@esbuild/linux-loong640.25.0indirect
npm@esbuild/linux-mips64el0.25.0indirect
npm@esbuild/linux-ppc640.25.0indirect
npm@esbuild/linux-riscv640.25.0indirect
npm@esbuild/linux-s390x0.25.0indirect
npm@esbuild/linux-x640.25.0indirect
npm@esbuild/netbsd-arm640.25.0indirect
npm@esbuild/netbsd-x640.25.0indirect
npm@esbuild/openbsd-arm640.25.0indirect
npm@esbuild/openbsd-x640.25.0indirect
npm@esbuild/sunos-x640.25.0indirect
npm@esbuild/win32-arm640.25.0indirect
npm@esbuild/win32-ia320.25.0indirect
npm@esbuild/win32-x640.25.0indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@oxc-project/types0.143.0indirect
npm@rolldown/binding-android-arm641.2.3indirect
npm@rolldown/binding-darwin-arm641.2.3indirect
npm@rolldown/binding-darwin-x641.2.3indirect
npm@rolldown/binding-freebsd-x641.2.3indirect
npm@rolldown/binding-linux-arm-gnueabihf1.2.3indirect
npm@rolldown/binding-linux-arm64-gnu1.2.3indirect
npm@rolldown/binding-linux-arm64-musl1.2.3indirect
npm@rolldown/binding-linux-ppc64-gnu1.2.3indirect
npm@rolldown/binding-linux-s390x-gnu1.2.3indirect
npm@rolldown/binding-linux-x64-gnu1.2.3indirect
npm@rolldown/binding-linux-x64-musl1.2.3indirect
npm@rolldown/binding-openharmony-arm641.2.3indirect
npm@rolldown/binding-win32-arm64-msvc1.2.3indirect
npm@rolldown/binding-win32-x64-msvc1.2.3indirect
npm@rolldown/pluginutils1.0.1indirect
npm@types/node20.19.43indirect
npmansi-styles6.1.0indirect
npmbraces3.0.3indirect
npmcoc-test0.1.2indirect
npmcoc.nvim0.0.83-next.25indirect
npmesbuild0.25.0indirect
npmfast-glob3.3.3indirect
npmfastq1.20.1indirect
npmfflate0.8.3indirect
npmfill-range7.1.1indirect
npmfs-extra10.0.0indirect
npmglob-parent5.1.2indirect
npmgraceful-fs4.2.9indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmjsonfile6.1.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.8indirect
npmpicomatch2.3.2indirect
npmqueue-microtask1.2.3indirect
npmrequest-light0.5.7indirect
npmreusify1.1.0indirect
npmrolldown1.2.3indirect
npmrun-parallel1.2.0indirect
npmto-regex-range5.0.1indirect
npmtypescript5.7.3indirect
npmundici-types6.21.0indirect
npmuniversalify2.0.0indirect
Dependency advisories 0

Installing npm:coc-yaml@1.9.3 pulls in 1 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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with neoclide/coc-yaml. Read them side by side →

80coc-plugin/coc-vscode-loaderRun VS Code extensions seamlessly in coc.nvimExcellent65neoclide/coc-javaJava extension for coc.nvimGood84ndonfris/fish-lspLSP implementation for the fish shell language 🐠Excellent73vscode-neovim/vscode-neovimVim mode for VSCode, powered by NeovimGood94neovim/nvim-lspconfigQuickstart configs for Nvim LSPExceptional94junegunn/fzf:cherry_blossom: A command-line fuzzy finderExceptional

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.