Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 17:42 UTC

kreuzberg-dev / kreuzberg-lts

Kreuzberg v4 LTS — long-term support for the v4 line (legacy; superseded by xberg for v5+). MIT-licensed.

Rust · HTMLMIT★ 10 stars⑂ 1 forksince Jul 2026View on GitHub ↗
KindNetwork serviceLibraryhow this is determined

kreuzberg-dev/kreuzberg-lts holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (86/100) and lowest on Community & Adoption (34/100). It was last updated 9 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Kreuzberg.devOrganization
1 follower3 public repossince Jun 2026

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

Package ecosystems

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
28.8/36Push recencylast push 9 days ago
29.1/36Commit cadence42/52 weeks with commits
18/18Commit volume4,133 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year4,133
human_commit_share1
days_since_last_push9
active_weeks_last_year42
How it's scored
27/27Ships releases3 releases published
36/36Release recencylatest release 41 days ago
27/27Release cadencea release every ~0.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count3
latest_release_tagv4.10.2
releases_from_tagsno
days_since_latest_release41
mean_days_between_releases0.7

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

34At Risk · 17% of overall
How it's scored
15.5/60Stars10 stars
0/25Forks1 forks
0/15Watchers1 watchers
Inputs used
forks1
stars10
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges19
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
4/80Monthly downloads1 downloads/month across go, packagist
0/20Registry dependents0 packages depend on it
Inputs used
packageskreuzberg/kreuzberg, github.com/kreuzberg-dev/kreuzberg-lts/v4
dependents0
ecosystemsgo, packagist
total_downloads1
monthly_downloads1
unverified_packages_excluded

Sustainability & Governance

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

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.5/22.5Commit distributiontop contributor authored 94% of commits
13.5/13.5Contributor breadth36 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled36
top_contributor_share0.935
How it's scored
0/42Issue resolutionno issues or no data
30/30PR acceptance2/2 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/25 approved changesets -- score normalized to 0
Inputs used
merged_prs2
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
2.2/25Owner reach1 followers of kreuzberg-dev
4.7/25Track record3 public repos, account ~0 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_loginkreuzberg-dev
public_repos3
account_age_days58

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable2 package(s) on go, packagist
35/35Publish recencylatest publish 41 days ago
20/20Version history120 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageskreuzberg/kreuzberg, github.com/kreuzberg-dev/kreuzberg-lts/v4
ecosystemsgo, packagist
any_deprecatedno
min_days_since_publish41

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
16/16Linter config.golangci.yml, .php-cs-fixer.dist.php, .php-cs-fixer.php, .rubocop.yml, phpstan.neon, pyproject.toml ([tool.ruff]), rustfmt.toml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests2 out of 2 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 sitehttps://kreuzberg.dev
10/10Repository description
10/10Topics12 topics
0/10Wiki
Inputs used
topicsdata-extraction, document-intelligence, document-parsing, docx, lts, ocr, pdf, pdf-extraction, rag, rust, tesseract, text-extraction
has_wikino
homepagehttps://kreuzberg.dev
docs_sitehttps://kreuzberg.dev
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests2 out of 2 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/7.5Code-ReviewFound 0/25 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 11 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities79 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4

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.

71Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://kreuzberg.dev/llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://kreuzberg.dev/llms.txt
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapTaskfile.yml, crates/kreuzberg-ffi/tests/c/Makefile, e2e/c/Makefile
22/22Automated tests
11/11Lint / format config.golangci.yml, .php-cs-fixer.dist.php, .php-cs-fixer.php, .rubocop.yml, phpstan.neon, pyproject.toml ([tool.ruff]), rustfmt.toml
11/11Static type checkingcrates/kreuzberg-node/tsconfig.json, crates/kreuzberg-wasm/tsconfig.json, docs-site/tsconfig.json, e2e/typescript/tsconfig.json, e2e/wasm/tsconfig.json, packages/python/kreuzberg/py.typed, packages/typescript/core/tsconfig.json, packages/typescript/test-utils/tsconfig.json, tsconfig.json
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock, Gemfile.lock, composer.lock, go.sum, mix.lock, pnpm-lock.yaml, uv.lock
has_dockerfileyes
typed_languageyes
bootstrap_filesTaskfile.yml, crates/kreuzberg-ffi/tests/c/Makefile, e2e/c/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configscrates/kreuzberg-node/tsconfig.json, crates/kreuzberg-wasm/tsconfig.json, docs-site/tsconfig.json, e2e/typescript/tsconfig.json, e2e/wasm/tsconfig.json, packages/python/kreuzberg/py.typed, packages/typescript/core/tsconfig.json, packages/typescript/test-utils/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifestsCargo.toml, crates/kreuzberg-cli/Cargo.toml, crates/kreuzberg-ffi/Cargo.toml, crates/kreuzberg-node/Cargo.toml, crates/kreuzberg-paddle-ocr/Cargo.toml, crates/kreuzberg-pdfium-render/Cargo.toml, crates/kreuzberg-php/Cargo.toml, crates/kreuzberg-py/Cargo.toml, crates/kreuzberg-tesseract/Cargo.toml, crates/kreuzberg-wasm/Cargo.toml, crates/kreuzberg-wasm/e2e/elixir/mix.exs, crates/kreuzberg-wasm/e2e/go/go.mod, crates/kreuzberg-wasm/e2e/java/pom.xml, crates/kreuzberg/Cargo.toml, e2e/csharp/Kreuzberg.E2E.Tests.csproj, e2e/csharp/Kreuzberg.E2E.csproj, e2e/elixir/mix.exs, e2e/go/go.mod, e2e/java/pom.xml, e2e/rust/Cargo.toml, packages/csharp/Benchmark/Benchmark.csproj, packages/csharp/Kreuzberg.Tests/Kreuzberg.Tests.csproj, packages/csharp/Kreuzberg/Kreuzberg.csproj, packages/elixir/mix.exs, packages/elixir/native/kreuzberg_rustler/Cargo.toml, packages/java/pom.xml, packages/r/src/rust/Cargo.toml, packages/ruby/ext/kreuzberg_rb/native/Cargo.toml, test_documents/data_formats/cargo.toml, v4/go.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
54.3/55Manageable file sizes28/2,122 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes529,118
source_files_sampled2,122
oversized_source_files28
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examplesnotebooks
Inputs used
example_dirsnotebooks
has_mcp_signalyes
api_schema_files
interfaces_expected_ofnetwork-service

Key facts

10GitHub stars
36contributors
4,133commits, last 12 months
9days since last push
3releases
1bus factor
0open issues
crates.io, Go, npm, Packagist, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-22 17:40 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/25 approved changesets -- score normalized to 0
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities79 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
npm@astrojs/starlight^0.41.3docs-site/package.json
npm@mermaid-js/layout-elk^0.2.2docs-site/package.json
npm@xberg-io/docs-theme^0.2.0docs-site/package.json
npmastro^7.0.7docs-site/package.json
npmastro-mermaid^2.1.0docs-site/package.json
npmmermaid^11.16.0docs-site/package.json
npmsharp^0.35.3docs-site/package.json
npmstarlight-llms-txt^0.11.0docs-site/package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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 statisticsPackagist, Go.