Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-18 00:34 UTC

grindlemire / go-search

A pure go lucene parser with no dependencies.

GoApache-2.0★ 51 stars⑂ 18 forkssince Nov 2022View on GitHub ↗

grindlemire/go-search holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Vitality (83/100) and lowest on Security (42/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

62
overall / 100
Moderate

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.

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

Ownership

Joel HolsteenPersonal account
40 followers62 public repossince Feb 2014Google

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gogithub.com/grindlemire/go-lucenepoints to another repo — not scoredv0.2.1-363 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
8.3/36Commit cadence12/52 weeks with commits
17.4/18Commit volume86 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year86
human_commit_share
days_since_last_push3
active_weeks_last_year12

Release discipline

100Exceptional
How it's scored
27/27Ships releases36 releases published
36/36Release recencylatest release 3 days ago
27/27Release cadencea release every ~20 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count36
latest_release_tagv0.2.1
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases20
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?

45Weak · 17% of overall
How it's scored
27.6/60Stars51 stars
10.3/25Forks18 forks
1.7/15Watchers3 watchers
Inputs used
forks18
stars51
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
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?

53Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.6/22.5Commit distributiontop contributor authored 93% of commits
13.5/13.5Contributor breadth11 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled11
top_contributor_share0.927
How it's scored
37.8/42Issue resolution90% of issues closed
27.1/30PR acceptance37/41 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/3 approved changesets -- score normalized to 0
Inputs used
merged_prs37
open_issues2
closed_issues18
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.9
closed_unmerged_prs4
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
11.6/25Owner reach40 followers of grindlemire
25/25Track record62 public repos, account ~12 yr old
Inputs used
followers40
owner_typeUser
is_verified
owner_logingrindlemire
public_repos62
account_age_days4,524
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests3 out of 4 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicslucene, parser, search, go
has_wikiyes
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?

42Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.8/2.5CI-Tests3 out of 4 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/3 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 5 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
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities36 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. 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.

53Moderate · 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
11/11Static type checkingGo (statically typed)
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_languageyes
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
45/45Type-checkable codeGo (statically typed)
55/55Manageable file sizes0/27 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes27,215
source_files_sampled27
oversized_source_files0

Key facts

51GitHub stars
11contributors
86commits, last 12 months
3days since last push
36releases
1bus factor
2open issues
Gopackage ecosystems

Data collection warnings

  • Could not fetch go package 'github.com/grindlemire/go-lucene/fuzz' from its registry
  • go package 'github.com/grindlemire/go-lucene' points at a different repository (https://github.com/grindlemire/go-lucene); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 4.2 / 10
4.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-07-18 00:34 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
7CI-Tests3 out of 4 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/3 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 5 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
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities36 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Gogithub.com/grindlemire/go-lucenev0.0.14fuzz/go.mod
Gogithub.com/pganalyze/pg_query_go/v4v4.2.3fuzz/go.mod
All dependencies 59

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

RegistryPackageVersionRelation
Gogithub.com/pganalyze/pg_query_go/v4v4.2.3direct
Godario.cat/mergov1.0.0indirect
Gofilippo.io/edwards25519v1.1.0indirect
Gogithub.com/azure/go-ansitermv0.0.0-20210617225240-d185dfc1b5a1indirect
Gogithub.com/cenkalti/backoff/v4v4.2.1indirect
Gogithub.com/containerd/containerdv1.7.18indirect
Gogithub.com/containerd/logv0.1.0indirect
Gogithub.com/containerd/platformsv0.2.1indirect
Gogithub.com/cpuguy83/dockercfgv0.3.1indirect
Gogithub.com/distribution/referencev0.6.0indirect
Gogithub.com/docker/dockerv27.1.1+incompatibleindirect
Gogithub.com/docker/go-connectionsv0.5.0indirect
Gogithub.com/docker/go-unitsv0.5.0indirect
Gogithub.com/dustin/go-humanizev1.0.1indirect
Gogithub.com/felixge/httpsnoopv1.0.4indirect
Gogithub.com/go-logr/logrv1.4.1indirect
Gogithub.com/go-logr/stdrv1.2.2indirect
Gogithub.com/go-ole/go-olev1.2.6indirect
Gogithub.com/go-sql-driver/mysqlv1.8.1indirect
Gogithub.com/gogo/protobufv1.3.2indirect
Gogithub.com/golang/protobufv1.4.2indirect
Gogithub.com/google/uuidv1.6.0indirect
Gogithub.com/klauspost/compressv1.17.4indirect
Gogithub.com/lufia/plan9statsv0.0.0-20211012122336-39d0f177ccd0indirect
Gogithub.com/magiconair/propertiesv1.8.7indirect
Gogithub.com/mattn/go-isattyv0.0.20indirect
Gogithub.com/microsoft/go-winiov0.6.2indirect
Gogithub.com/moby/docker-image-specv1.3.1indirect
Gogithub.com/moby/patternmatcherv0.6.0indirect
Gogithub.com/moby/sys/sequentialv0.5.0indirect
Gogithub.com/moby/sys/userv0.1.0indirect
Gogithub.com/moby/termv0.5.0indirect
Gogithub.com/morikuni/aecv1.0.0indirect
Gogithub.com/ncruces/go-strftimev1.0.0indirect
Gogithub.com/opencontainers/go-digestv1.0.0indirect
Gogithub.com/opencontainers/image-specv1.1.0indirect
Gogithub.com/pkg/errorsv0.9.1indirect
Gogithub.com/power-devops/perfstatv0.0.0-20210106213030-5aafc221ea8cindirect
Gogithub.com/remyoudompheng/bigfftv0.0.0-20230129092748-24d4a6f8daecindirect
Gogithub.com/shirou/gopsutil/v3v3.23.12indirect
Gogithub.com/shoenig/go-m1cpuv0.1.6indirect
Gogithub.com/sirupsen/logrusv1.9.3indirect
Gogithub.com/testcontainers/testcontainers-gov0.33.0indirect
Gogithub.com/testcontainers/testcontainers-go/modules/mysqlv0.33.0indirect
Gogithub.com/tklauser/go-sysconfv0.3.12indirect
Gogithub.com/tklauser/numcpusv0.6.1indirect
Gogithub.com/yusufpapurcu/wmiv1.2.3indirect
Gogo.opentelemetry.io/contrib/instrumentation/net/http/otelhttpv0.49.0indirect
Gogo.opentelemetry.io/otelv1.24.0indirect
Gogo.opentelemetry.io/otel/metricv1.24.0indirect
Gogo.opentelemetry.io/otel/tracev1.24.0indirect
Gogolang.org/x/cryptov0.24.0indirect
Gogolang.org/x/sysv0.21.0indirect
Gogolang.org/x/sysv0.42.0indirect
Gogoogle.golang.org/protobufv1.23.0indirect
Gomodernc.org/libcv1.70.0indirect
Gomodernc.org/mathutilv1.7.1indirect
Gomodernc.org/memoryv1.11.0indirect
Gomodernc.org/sqlitev1.48.1indirect
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.12.0 — full methodology · metrics wiki.

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