Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 22:24 UTC

elastic / elasticsearch-js

Official Elasticsearch client library for Node.js

TypeScriptApache-2.0★ 5,288 stars⑂ 723 forkssince Jun 2013View on GitHub ↗

elastic/elasticsearch-js holds a health index of 98 out of 100, placing it in the Exceptional band. It scores highest on Community & Adoption (99/100) and lowest on Security (73/100). It was last updated 5 days ago. 2 contributors account for most of its recent work.

98
overall / 100
Exceptional

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.

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

Ownership

elasticOrganization
5,549 followers961 public repossince Feb 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@elastic/elasticsearch9.5.19,804,52621219 days agoelasticsearchelastickibanamappingrestsearchclientindex

Metrics by category

Vitality

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

98Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
31.8/36Commit cadence — 46/52 weeks with commits
18/18Commit volume — 155 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year155
human_commit_share0.73
days_since_last_push5
active_weeks_last_year46

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 19 days ago
27/27Release cadence — a release every ~21.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv9.5.1
releases_from_tagsno
days_since_latest_release19
mean_days_between_releases21.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?

99Exceptional · 17% of overall
How it's scored
60/60Stars — 5,288 stars
23.8/25Forks — 723 forks
14.5/15Watchers — 403 watchers
Inputs used
forks723
stars5,288
watchers403
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 9,804,526 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@elastic/elasticsearch
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads9,804,526
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?

80Excellent · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.1/22.5Commit distribution — top contributor authored 42% of commits
13.5/13.5Contributor breadth — 95 contributors
10/10OpenSSF Scorecard: Contributors — project has 15 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled95
top_contributor_share0.416
How it's scored
41.3/42Issue resolution — 98% of issues closed
25.9/30PR acceptance — 2,030/2,352 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-Review — Found 7/16 approved changesets -- score normalized to 4
Inputs used
merged_prs2,030
open_issues18
closed_issues1,050
prs_merged_7d0
prs_decided_7d0
prs_merged_30d6
prs_decided_30d7
issue_closed_ratio0.983
closed_unmerged_prs322
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
25/25Owner reach — 5,549 followers of elastic
25/25Track record — 961 public repos, account ~12 yr old
Inputs used
followers5,549
owner_typeOrganization
is_verifiedno
owner_loginelastic
public_repos961
account_age_days4,591

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 19 days ago
20/20Version history — 212 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@elastic/elasticsearch
ecosystemsnpm
any_deprecatedno
min_days_since_publish19

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://ela.st/js-client
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicselasticsearch, nodejs, client, rest, javascript
has_wikino
homepagehttps://ela.st/js-client
docs_sitehttps://ela.st/js-client
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

73Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 7/16 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 15 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
7.5/7.5Maintained — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
2/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file 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_aggregate6.6
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_packages10
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:@elastic/elasticsearch@9.5.1 runtime dependency closure — what installing the published package pulls in — 10 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.

80Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 72 of 73 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.986
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes2,320
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.mjs
11/11Static type checking — test/esm/fixtures/tsconfig.json, tsconfig.json
10/10Reproducible environment — Dockerfile
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
4/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstest/esm/fixtures/tsconfig.json, tsconfig.json
agent_commit_share0.02
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
52.4/55Manageable file sizes — 7/146 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes2,183,106
source_files_sampled146
oversized_source_files7
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
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

5,288GitHub stars
95contributors
155commits, last 12 months
5days since last push
100releases
2bus factor
18open 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 ★ / 723 ⇿
0Stars
723Forks
100Releases

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.

012525037550062575071192013-122020-052026-09
Major 2Minor 37Patch 55

Each point covers 12 days.

OpenSSF Scorecard 6.6 / 10
6.6aggregate

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-19 22:24 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-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
4Code-ReviewFound 7/16 approved changesets -- score normalized to 4
10Contributorsproject has 15 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npm@elastic/transport^9.4.0package.json
npmtslib^2.4.0package.json
All dependencies 41

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

RegistryPackageVersionRelation
npm@elastic/transport^9.4.0direct
npmtslib^2.4.0direct
npm@elastic/elasticsearch^8.0.0indirect
npm@elastic/elasticsearch-mock^0.3.1indirect
npm@elastic/request-converter9.3.0indirect
npm@opentelemetry/sdk-trace-base1.30.1indirect
npm@sinonjs/fake-timers14.0.0indirect
npm@types/debug4.1.13indirect
npm@types/ms2.1.0indirect
npm@types/node22.19.19indirect
npm@types/sinonjs__fake-timers8.1.5indirect
npm@types/split24.2.3indirect
npm@types/stoppable1.1.3indirect
npmapache-arrow21.1.0indirect
npmc810.1.3indirect
npmcross-zip4.0.1indirect
npmdesm1.3.1indirect
npmeslint9.39.5indirect
npminly5.0.1indirect
npmjs-yaml4.1.1indirect
npmjsfuzz1.0.15indirect
npmlicense-checker25.0.1indirect
npmminimist1.2.8indirect
npmms2.1.3indirect
npmneostandard0.13.0indirect
npmnode-abort-controller3.1.1indirect
npmora9.0.0indirect
npmproxy2.2.0indirect
npmrimraf6.1.2indirect
npmsemver7.7.3indirect
npmsplit24.2.0indirect
npmstandard^16.0.3indirect
npmstoppable1.1.0indirect
npmtap21.5.0indirect
npmtap^15.0.9indirect
npmts-node10.9.2indirect
npmtsc-esm-fix3.1.2indirect
npmtypescript5.9.3indirect
npmworkq3.0.0indirect
npmxmlbuilder24.0.3indirect
npmzx8.8.5indirect
Dependency advisories 0

Installing npm:@elastic/elasticsearch@9.5.1 pulls in 10 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.