Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-19 00:52 UTC

elastic / logstash

Logstash - transport and process your logs, events, or other data

Java · RubyCustom license★ 14,983 stars⑂ 3,502 forkssince Nov 2010View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

elastic/logstash holds a health index of 98 out of 100, placing it in the Exceptional band. It scores highest on AI Readiness (100/100) and lowest on Sustainability & Governance (72/100). It was last updated today. 4 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 86 is calibrated to 98 on the published index scale (record calibration 2026-08-02).

Ownership

elasticOrganization
5,807 followers977 public repossince Feb 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemslogstash-corepoints to another repo — not scored7.5.2-2232493 days ago
RubyGemslogstash-core-plugin-apipoints to another repo — not scored2.1.28-493278 days ago
RubyGemspaquet0.2.1-33526 days ago

Metrics by category

Vitality

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

99Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
34.6/36Commit cadence — 50/52 weeks with commits
18/18Commit volume — 324 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year324
human_commit_share0.71
days_since_last_push0
active_weeks_last_year50

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 8 days ago
27/27Release cadence — a release every ~6.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv8.19.25
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases6.2
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?

87Excellent · 17% of overall

Popularity & adoption

100Exceptional
How it's scored
60/60Stars — 14,983 stars
25/25Forks — 3,502 forks
15/15Watchers — 793 watchers
Inputs used
forks3,502
stars14,983
watchers793
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes
How it's scored
71.4/80Total downloads — 7,450,069 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespaquet
dependents—
ecosystemsrubygems
total_downloads7,450,069
monthly_downloads—
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?

72Good · 23% of overall
How it's scored
43.2/54Bus factor — 4 contributor(s) cover half of all commits
13.9/22.5Commit distribution — top contributor authored 38% of commits
13.5/13.5Contributor breadth — 95 contributors
10/10OpenSSF Scorecard: Contributors — project has 19 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled95
top_contributor_share0.382
How it's scored
30.3/42Issue resolution — 72% of issues closed
18.5/30PR acceptance — 7,611/12,374 decided PRs merged
0/13Newcomer PR acceptance — 0/2 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs7,611
open_issues1,997
closed_issues5,164
prs_merged_7d8
prs_decided_7d10
prs_merged_30d8
prs_decided_30d10
issue_closed_ratio0.721
closed_unmerged_prs4,763
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
25/25Owner reach — 5,807 followers of elastic
25/25Track record — 977 public repos, account ~12 yr old
Inputs used
followers5,807
owner_typeOrganization
is_verifiedno
owner_loginelastic
public_repos977
account_age_days4,651
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
4/35Publish recency — latest publish 3,526 days ago
12/20Version history — 3 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespaquet
ecosystemsrubygems
any_deprecatedno
min_days_since_publish3,526

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall
How it's scored
24/24CI workflows — 29 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
9.6/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_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://www.elastic.co/products/logstash
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicsetl-framework, streaming, logging, java, jruby, real-time-processing
has_wikino
homepagehttps://www.elastic.co/products/logstash
docs_sitehttps://www.elastic.co/products/logstash
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

78Good · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 19 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.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate7.2
Excluded from scoring (no data or not applicable): Packaging, Pinned-Dependencies, 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
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
advisories0
affected_packages0
assessed_packages4
unassessed_packages44
affected_by_severitynone
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 4 resolved dependencies against OSV. 44 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

100Exceptional · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md, qa/AGENTS.md, qa/CLAUDE.md, x-pack/AGENTS.md, x-pack/CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://www.elastic.co/llms.txt)
40/40Legible commit history — 68 of 71 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.elastic.co/llms.txt
legible_history_share0.958
agent_instruction_filesAGENTS.md, CLAUDE.md, qa/AGENTS.md, qa/CLAUDE.md, x-pack/AGENTS.md, x-pack/CLAUDE.md
agent_instruction_max_bytes24,429
How it's scored
18/18One-command bootstrap — .ci/Makefile, docker/Makefile, qa/integration/fixtures/offline_wrapper/Makefile
22/22Automated tests
11/11Lint / format config — .rubocop.yml
11/11Static type checking — Java (statically typed)
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 16 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 8 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageyes
bootstrap_files.ci/Makefile, docker/Makefile, qa/integration/fixtures/offline_wrapper/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.16
toolchain_manifestsbuild.gradle, buildSrc/build.gradle, docker/data/logstash/env2yaml/build.gradle, logstash-core/benchmarks/build.gradle, logstash-core/build.gradle, qa/integration/build.gradle, tools/benchmark-cli/build.gradle, tools/dependencies-report/build.gradle, tools/jvm-options-parser/build.gradle, x-pack/build.gradle
dependency_bot_commit_share0.08
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — Java (statically typed)
54.8/55Manageable file sizes — 4/1,217 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes81,725
source_files_sampled1,217
oversized_source_files4
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

14,983GitHub stars
95contributors
324commits, last 12 months
0days since last push
100releases
4bus factor
1,997open issues
Maven, RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • rubygems package 'logstash-core' points at a different repository (http://www.elastic.co/guide/en/logstash/current/index.html); excluded from ecosystem scoring
  • rubygems package 'logstash-core-plugin-api' points at a different repository (http://www.elastic.co/guide/en/logstash/current/index.html); excluded from ecosystem scoring
  • Could not fetch rubygems package 'logstash-filter-dummy' from its registry
  • Could not fetch rubygems package 'logstash-integration-tests' from its registry
  • Could not fetch rubygems package 'logstash-docgen' from its registry

More detail

Star and fork history 0 ★ / 3,502 ⇿
0Stars
3,502Forks
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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

2,4002,6002,8003,0003,2003,4003,6003,502122019-122023-052026-11
Major 1Minor 7Patch 91

Each point covers 7 days.

OpenSSF Scorecard 7.2 / 10
7.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-11-19 00:51 UTC

9Binary-Artifactsbinaries present in source code
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
10Code-Reviewall changesets reviewed
10Contributorsproject has 19 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesinternal error: internal error: invalid Dockerfile: Syntax error - can't find = in "locale". Must be of the form: name=value
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 7
RegistryPackageVersion constraintManifest
RubyGemsrspec~> 3.13qa/Gemfile
RubyGemsrake—qa/Gemfile
RubyGemsstud—qa/Gemfile
RubyGemsdocker-api—qa/Gemfile
RubyGemsbase64—qa/Gemfile
RubyGemslogstash-core—qa/integration/Gemfile
RubyGemslogstash-core-plugin-api—qa/integration/Gemfile
All dependencies 48

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

RegistryPackageVersionRelation
RubyGemsbase64—direct
RubyGemsdocker-api—direct
RubyGemslogstash-core—direct
RubyGemslogstash-core-plugin-api—direct
RubyGemsrake—direct
RubyGemsrspec—direct
RubyGemsstud—direct
PyPIpyyaml6.0.2indirect
PyPIrequests2.33.0indirect
RubyGemsaddressable—indirect
RubyGemsasciidoctor—indirect
RubyGemsbigdecimal—indirect
RubyGemschildprocess—indirect
RubyGemsclamp—indirect
RubyGemsconcurrent-ruby—indirect
RubyGemscsv—indirect
RubyGemsdown—indirect
RubyGemselasticsearch—indirect
RubyGemsfilesize—indirect
RubyGemsflores—indirect
RubyGemsflores0.0.8indirect
RubyGemsgemoji—indirect
RubyGemsgems—indirect
RubyGemsgit—indirect
RubyGemsi18n—indirect
RubyGemsjruby-openssl—indirect
RubyGemslogstash-devutils—indirect
RubyGemslogstash-devutils0.0.6indirect
RubyGemslogstash-filter-geoip—indirect
RubyGemslogstash-input-packtestdep—indirect
RubyGemsmanticore—indirect
RubyGemsminitar—indirect
RubyGemsmulti_json—indirect
RubyGemsobserver—indirect
RubyGemsoctokit—indirect
RubyGemspaquet—indirect
RubyGemspry—indirect
RubyGemspuma—indirect
RubyGemsrack—indirect
RubyGemsrspec-wait—indirect
RubyGemsrubyzip—indirect
RubyGemssinatra—indirect
RubyGemsthread_safe—indirect
RubyGemsthwait—indirect
RubyGemstreetop—indirect
RubyGemstzinfo-data—indirect
RubyGemsvcr—indirect
RubyGemswebmock—indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 4 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 44 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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 — RubyGems.