Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-22 00:38 UTC

projectblacklight / blacklight

Blacklight provides a discovery interface for any Solr (http://lucene.apache.org/solr) index.

RubyCustom license★ 790 stars⑂ 251 forkssince Oct 2009View on GitHub ↗
KindLibraryNetwork servicehow this is determined

projectblacklight/blacklight holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Vitality (84/100) and lowest on AI Readiness (40/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

90
overall / 100
Excellent

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.

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

Ownership

Project BlacklightOrganization
51 followers34 public repossince Aug 2009

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmblacklight-frontend9.0.04,12569238 days ago
RubyGemsblacklight9.0.0-279238 days ago

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
24.2/36Commit cadence35/52 weeks with commits
18/18Commit volume238 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year238
human_commit_share1
days_since_last_push1
active_weeks_last_year35
How it's scored
27/27Ships releases100 releases published
16.2/36Release recencylatest release 238 days ago
27/27Release cadencea release every ~23.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv9.0.0
releases_from_tagsno
days_since_latest_release238
mean_days_between_releases23.5
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?

71Good · 17% of overall
How it's scored
47/60Stars790 stars
20/25Forks251 forks
9.9/15Watchers62 watchers
Inputs used
forks251
stars790
watchers62
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
16.9/22.5Licenselicense 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_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
48.2/80Monthly downloads4,125 downloads/month across npm, rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesblacklight-frontend, blacklight
dependents
ecosystemsnpm, rubygems
total_downloads1,891,838
monthly_downloads4,125
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 factor2 contributor(s) cover half of all commits
14.6/22.5Commit distributiontop contributor authored 35% of commits
13.5/13.5Contributor breadth93 contributors
10/10OpenSSF Scorecard: Contributorsproject has 60 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled93
top_contributor_share0.351
How it's scored
37.5/42Issue resolution89% of issues closed
26.8/30PR acceptance2,261/2,530 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs2,261
open_issues136
closed_issues1,152
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.894
closed_unmerged_prs269
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
12.3/25Owner reach51 followers of projectblacklight
23.2/25Track record34 public repos, account ~16 yr old
Inputs used
followers51
owner_typeOrganization
is_verified
owner_loginprojectblacklight
public_repos34
account_age_days6,171
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable2 package(s) on npm, rubygems
26/35Publish recencylatest publish 238 days ago
20/20Version history279 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesblacklight-frontend, blacklight
ecosystemsnpm, rubygems
any_deprecatedno
min_days_since_publish238

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests16 out of 16 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
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttp://projectblacklight.org/
10/10Repository description
10/10Topics5 topics
10/10Wiki
Inputs used
topicssolr, ruby, discovery-interface, rails-engine, blacklight
has_wikiyes
homepagehttp://projectblacklight.org/
docs_sitehttp://projectblacklight.org/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

69Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests16 out of 16 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
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 60 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 4 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
4.5/5SASTSAST tool is not run on all commits -- score normalized to 9
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
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:blacklight-frontend@9.0.0 runtime dependency closure — what installing the published package pulls in — 1 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.

40Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
28.8/40Legible commit history54 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.54
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/387 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes45,844
source_files_sampled387
oversized_source_files0

Key facts

790GitHub stars
93contributors
238commits, last 12 months
1days since last push
100releases
2bus factor
136open issues
npm, RubyGemspackage ecosystems

More detail

Star and fork history 790 ★ / 251 ⇿
790Stars
251Forks
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.

0200400600800790247772009-102018-032026-07
Major 3Minor 60Patch 28

Each point covers 16 days.

OpenSSF Scorecard 6.1 / 10
6.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-22 00:38 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
10CI-Tests16 out of 16 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 60 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 4 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
9SASTSAST tool is not run on all commits -- score normalized to 9
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
RubyGemsrailsGemfile
RubyGemsrailsGemfile
RubyGemseasy_translate~> 0.5.1Gemfile
npmbootstrap>=5.3.5 <6.0.0package.json
All dependencies 33

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

RegistryPackageVersionRelation
npmbootstrap>=5.3.5 <6.0.0direct
npmbootstrap^5.3.8direct
RubyGemseasy_translatedirect
RubyGemsrailsdirect
npmrollup^4.24.0indirect
npmrollup-plugin-includepaths^0.2.4indirect
npmsass^1.80.3indirect
RubyGemsactiverecord-jdbcsqlite3-adapterindirect
RubyGemsaxe-core-rspecindirect
RubyGemscapybaraindirect
RubyGemsengine_cartindirect
RubyGemsequivalent-xmlindirect
RubyGemsglobalidindirect
RubyGemsi18nindirect
RubyGemsi18n-tasksindirect
RubyGemsjbuilderindirect
RubyGemskaminariindirect
RubyGemsostructindirect
RubyGemsrsolrindirect
RubyGemsrspec-benchmarkindirect
RubyGemsrspec-collection_matchersindirect
RubyGemsrspec-railsindirect
RubyGemsrubocopindirect
RubyGemsrubocop-capybaraindirect
RubyGemsrubocop-factory_botindirect
RubyGemsrubocop-railsindirect
RubyGemsrubocop-rspecindirect
RubyGemsrubocop-rspec_railsindirect
RubyGemsselenium-webdriverindirect
RubyGemssimplecovindirect
RubyGemssolr_wrapperindirect
RubyGemsview_componentindirect
RubyGemszeitwerkindirect
Dependency advisories 0

Installing npm:blacklight-frontend@9.0.0 pulls in 1 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.26.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm, RubyGems.