Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-16 20:50 UTC

sublimelsp / LSP-file-watcher-chokidar

Chokidar-based file watcher implementation for LSP

Python · JavaScriptMIT★ 29 stars⑂ 1 forksince Jun 2021View on GitHub ↗

sublimelsp/LSP-file-watcher-chokidar holds a health index of 47 out of 100, placing it in the Weak band. It scores highest on Vitality (63/100) and lowest on Community & Adoption (37/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

47
overall / 100
Weak

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.

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

Ownership

SublimeLSPOrganization
124 followers96 public repossince Feb 2019

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?

63Moderate · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
4.8/36Commit cadence — 7/52 weeks with commits
11.1/18Commit volume — 16 commits in the last year
4/10OpenSSF Scorecard: Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year16
human_commit_share0.553
days_since_last_push2
active_weeks_last_year7
How it's scored
27/27Ships releases — 11 releases published
27/36Release recency — latest release 171 days ago
12.6/27Release cadence — a release every ~131.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count11
latest_release_tagv1.1.6
releases_from_tagsno
days_since_latest_release171
mean_days_between_releases131.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?

37Weak · 17% of overall
How it's scored
23.5/60Stars — 29 stars
0/25Forks — 1 forks
1.7/15Watchers — 3 watchers
Inputs used
forks1
stars29
watchers3
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

Sustainability & Governance

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

50Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.2/22.5Commit distribution — top contributor authored 86% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.857
How it's scored
30/42Issue resolution — 71% of issues closed
22.3/30PR acceptance — 32/43 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/12 approved changesets -- score normalized to 0
Inputs used
merged_prs32
open_issues2
closed_issues5
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.714
closed_unmerged_prs11
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 backing — organization-owned
0/20Verified domain
15.1/25Owner reach — 124 followers of sublimelsp
25/25Track record — 96 public repos, account ~7 yr old
Inputs used
followers124
owner_typeOrganization
is_verifiedno
owner_loginsublimelsp
public_repos96
account_age_days2,818

Engineering Quality

Are baseline engineering and documentation practices in place?

40Weak · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
0/24Tests present
16/16Linter config — eslint.config.mjs, pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 1 out of 29 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno
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?

48Weak · 16% of overall
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 — 1 out of 29 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/7.5Code-Review — Found 1/12 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
3/7.5Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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 — no data
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.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 advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages132
unassessed_packages0
affected_by_severitymoderate 1
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 132 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.

49Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
38.1/40Legible commit history — 15 of 21 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.714
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — eslint.config.mjs, pyproject.toml ([tool.ruff])
11/11Static type checking — chokidar/tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 38
8/8Automated maintenance — 17 of the last 38 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configschokidar/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.447
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
27/45Type-checkable code — Python with type-check config (chokidar/tsconfig.json)
55/55Manageable file sizes — 0/6 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes9,680
source_files_sampled6
oversized_source_files0

Key facts

29GitHub stars
3contributors
16commits, last 12 months
2days since last push
11releases
1bus factor
2open issues
npm, PyPIpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 3.5 / 10
3.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-11-16 20:50 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests1 out of 29 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/12 approved changesets -- score normalized to 0
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
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
npmchokidar3.6.0chokidar/package.json
npmlodash.debounce4.0.8chokidar/package.json
npmlodash.throttle4.1.1chokidar/package.json
All dependencies 132

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

RegistryPackageVersionRelation
npmchokidar3.6.0direct
npmlodash.debounce4.0.8direct
npmlodash.throttle4.1.1direct
npm@cacheable/memory2.2.0indirect
npm@cacheable/utils2.5.0indirect
npm@eslint-community/eslint-utils4.10.1indirect
npm@eslint-community/regexpp4.12.2indirect
npm@eslint/config-array0.23.5indirect
npm@eslint/config-helpers0.7.0indirect
npm@eslint/core1.2.1indirect
npm@eslint/eslintrc3.3.7indirect
npm@eslint/js10.0.1indirect
npm@eslint/object-schema3.0.5indirect
npm@eslint/plugin-kit0.7.3indirect
npm@humanfs/core0.19.2indirect
npm@humanfs/node0.16.8indirect
npm@humanfs/types0.15.0indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/retry0.4.3indirect
npm@keyv/bigmap1.3.1indirect
npm@keyv/serialize1.1.1indirect
npm@types/esrecurse4.3.1indirect
npm@types/estree1.0.9indirect
npm@types/json-schema7.0.15indirect
npm@types/lodash4.17.26indirect
npm@types/lodash.debounce4.0.9indirect
npm@types/lodash.throttle4.1.9indirect
npm@types/node26.6.5indirect
npm@typescript-eslint/eslint-plugin8.71.1indirect
npm@typescript-eslint/parser8.71.1indirect
npm@typescript-eslint/project-service8.71.1indirect
npm@typescript-eslint/scope-manager8.71.1indirect
npm@typescript-eslint/tsconfig-utils8.71.1indirect
npm@typescript-eslint/type-utils8.71.1indirect
npm@typescript-eslint/types8.71.1indirect
npm@typescript-eslint/typescript-estree8.71.1indirect
npm@typescript-eslint/utils8.71.1indirect
npm@typescript-eslint/visitor-keys8.71.1indirect
npmacorn8.19.0indirect
npmacorn-jsx5.3.2indirect
npmajv6.15.0indirect
npmanymatch3.1.3indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbalanced-match4.0.4indirect
npmbinary-extensions2.3.0indirect
npmbrace-expansion1.1.21indirect
npmbrace-expansion5.0.12indirect
npmbraces3.0.3indirect
npmcacheable2.5.0indirect
npmcallsites3.1.0indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdeep-is0.1.4indirect
npmescape-string-regexp4.0.0indirect
npmeslint10.12.0indirect
npmeslint-scope9.1.2indirect
npmeslint-visitor-keys3.4.3indirect
npmeslint-visitor-keys4.2.1indirect
npmeslint-visitor-keys5.0.1indirect
npmespree10.4.0indirect
npmespree11.2.0indirect
npmesquery1.7.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfdir6.5.0indirect
npmfile-entry-cache11.1.5indirect
npmfill-range7.1.1indirect
npmfind-up5.0.0indirect
npmflat-cache6.1.23indirect
npmflatted3.4.4indirect
npmfsevents2.3.3indirect
npmglob-parent5.1.2indirect
npmglob-parent6.0.2indirect
npmglobals14.0.0indirect
npmglobals17.13.0indirect
npmhashery1.5.1indirect
npmhookified1.15.1indirect
npmhookified2.2.0indirect
npmignore5.3.2indirect
npmignore7.0.12indirect
npmimport-fresh3.3.1indirect
npmimurmurhash0.1.4indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmisexe2.0.0indirect
npmjs-yaml4.3.2indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv5.6.0indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmminimatch10.2.6indirect
npmminimatch3.1.5indirect
npmms2.1.3indirect
npmnatural-compare1.4.0indirect
npmnormalize-path3.0.0indirect
npmoptionator0.9.4indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmparent-module1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmpicomatch2.3.2indirect
npmpicomatch4.0.7indirect
npmprelude-ls1.2.1indirect
npmpunycode2.3.1indirect
npmqified0.10.1indirect
npmreaddirp3.6.0indirect
npmresolve-from4.0.0indirect
npmsemver7.8.5indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmstrip-json-comments3.1.1indirect
npmtinyglobby0.2.17indirect
npmto-regex-range5.0.1indirect
npmts-api-utils2.5.0indirect
npmtype-check0.4.0indirect
npmtypescript6.0.3indirect
npmtypescript-eslint8.71.1indirect
npmundici-types8.9.0indirect
npmuri-js4.4.1indirect
npmwhich2.0.2indirect
npmword-wrap1.2.5indirect
npmyocto-queue0.1.0indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
minimatch10.2.6indirectmoderate111.0.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.34.0 — full methodology · metrics wiki.

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