Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-19 15:30 UTC

RediSearch / ftsb

Full Text Search Benchmark, a tool for comparing and evaluating full-text search engines.

Python · GoMIT★ 26 stars⑂ 4 forkssince Jul 2019View on GitHub ↗

RediSearch/ftsb holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (81/100) and lowest on Community & Adoption (38/100). It was last updated 5 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

RediSearchOrganization
92 followers19 public repossince Jan 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/RediSearch/ftsbv0.5.6-195 days ago

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
36/36Push recencylast push 5 days ago
4.8/36Commit cadence7/52 weeks with commits
13.6/18Commit volume32 commits in the last year
10/10OpenSSF Scorecard: Maintained29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year32
human_commit_share
days_since_last_push5
active_weeks_last_year7
How it's scored
27/27Ships releases21 releases published
36/36Release recencylatest release 5 days ago
19.8/27Release cadencea release every ~51.2 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count21
latest_release_tagv0.5.6
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases51.2

Community & Adoption

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

38Weak · 17% of overall
How it's scored
22.7/60Stars26 stars
4/25Forks4 forks
0/15Watchers2 watchers
Inputs used
forks4
stars26
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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

Sustainability & Governance

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

62Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.7/22.5Commit distributiontop contributor authored 84% of commits
12.2/13.5Contributor breadth9 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.836
How it's scored
12.3/42Issue resolution29% of issues closed
28.9/30PR acceptance80/83 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 5/12 approved changesets -- score normalized to 4
Inputs used
merged_prs80
open_issues24
closed_issues10
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.294
closed_unmerged_prs3
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
14.2/25Owner reach92 followers of RediSearch
21.5/25Track record19 public repos, account ~7 yr old
Inputs used
followers92
owner_typeOrganization
is_verified
owner_loginRediSearch
public_repos19
account_age_days2,735
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on go
35/35Publish recencylatest publish 5 days ago
20/20Version history19 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgithub.com/RediSearch/ftsb
ecosystemsgo
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://redisearch.io
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsredisearch, search-engines, benchmark, redis
has_wikiyes
homepagehttps://redisearch.io
docs_sitehttps://redisearch.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

51Moderate · 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-Tests11 out of 11 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
3/7.5Code-ReviewFound 5/12 approved changesets -- score normalized to 4
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not 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.5Vulnerabilities11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

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.

39Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePython without a type-check config
55/55Manageable file sizes0/42 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes33,731
source_files_sampled42
oversized_source_files0

Key facts

26GitHub stars
9contributors
32commits, last 12 months
5days since last push
21releases
1bus factor
24open issues
Gopackage ecosystems

More detail

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-07-19 15:29 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests11 out of 11 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 5/12 approved changesets -- score normalized to 4
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities11 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
Gocode.cloudfoundry.org/bytefmtv0.36.0go.mod
Gogithub.com/HdrHistogram/hdrhistogram-gov1.0.1go.mod
Gogithub.com/mediocregopher/radix/v3v3.8.1go.mod
Gogolang.org/x/timev0.0.0-20201208040808-7e3f01d25324go.mod
All dependencies 37

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

RegistryPackageVersionRelation
Gocode.cloudfoundry.org/bytefmt0.36.0direct
Gogithub.com/hdrhistogram/hdrhistogram-go1.0.1direct
Gogithub.com/mediocregopher/radix/v33.8.1direct
Gogolang.org/x/time0.0.0-20201208040808-7e3f01d25324direct
Gogithub.com/google/go-github17.0.0+incompatibleindirect
Gogithub.com/google/go-github/v6666.0.0indirect
Gogithub.com/google/go-querystring1.1.0indirect
Gogithub.com/hashicorp/go-version1.7.0indirect
Gogithub.com/inconshreveable/mousetrap1.1.0indirect
Gogithub.com/mattn/go-colorable0.1.13indirect
Gogithub.com/mattn/go-isatty0.0.20indirect
Gogithub.com/mitchellh/colorstring0.0.0-20190213212951-d06e56a500dbindirect
Gogithub.com/mitchellh/gox1.0.1indirect
Gogithub.com/mitchellh/iochan1.0.0indirect
Gogithub.com/songmu/retry0.1.0indirect
Gogithub.com/spf13/cobra1.8.1indirect
Gogithub.com/spf13/pflag1.0.5indirect
Gogithub.com/tcnksm/ghr0.17.0indirect
Gogithub.com/tcnksm/go-gitconfig0.1.2indirect
Gogithub.com/tcnksm/go-latest0.0.0-20170313132115-e3007ae9052eindirect
Gogithub.com/thediveo/enumflag/v22.0.5indirect
Gogolang.org/x/exp0.0.0-20241009180824-f66d83c29e7cindirect
Gogolang.org/x/net0.39.0indirect
Gogolang.org/x/oauth20.23.0indirect
Gogolang.org/x/sync0.8.0indirect
Gogolang.org/x/sys0.32.0indirect
Gogolang.org/x/xerrors0.0.0-20220609144429-65e65417b02findirect
PyPIboto3indirect
PyPIboto31.13.24indirect
PyPIcommon0.1.2indirect
PyPImatplotlib3.2.1indirect
PyPInumpy1.22.0indirect
PyPIpython-dateutil2.8.1indirect
PyPItdigest0.5.2.2indirect
PyPItqdmindirect
PyPItqdm4.30.0indirect
PyPIurllib3indirect
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.15.0 — full methodology · metrics wiki.

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