Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 07:09 UTC

xxsds / sdsl-lite

Succinct Data Structure Library 3.0

C++Custom license★ 110 stars⑂ 18 forkssince Nov 2016forkView on GitHub ↗

xxsds/sdsl-lite holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on AI Readiness (62/100) and lowest on Community & Adoption (35/100). It was last updated 80 days ago. A single contributor accounts for most of its recent work.

45
overall / 100
Weak

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.

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

Ownership

xxsdsOrganization
6 followers3 public repossince Mar 2016

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

Metrics by category

Vitality

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

53Moderate · 21% of overall
How it's scored
18/36Push recencylast push 80 days ago
4.2/36Commit cadence6/52 weeks with commits
11.7/18Commit volume19 commits in the last year
3/10OpenSSF Scorecard: Maintained3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year19
human_commit_share0.88
days_since_last_push80
active_weeks_last_year6
How it's scored
27/27Ships releases5 releases published
36/36Release recencylatest release 80 days ago
5.4/27Release cadencea release every ~426.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count5
latest_release_tagv3.0.4
releases_from_tagsno
days_since_latest_release80
mean_days_between_releases426.7
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?

35Weak · 17% of overall
How it's scored
33/60Stars110 stars
10.3/25Forks18 forks
5.8/15Watchers12 watchers
Inputs used
forks18
stars110
watchers12
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
16.9/22.5Licenselicense file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges0
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.5/22.5Commit distributiontop contributor authored 62% of commits
13.5/13.5Contributor breadth41 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled41
top_contributor_share0.622
How it's scored
30.9/42Issue resolution74% of issues closed
28.9/30PR acceptance104/108 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 1/5 approved changesets -- score normalized to 2
Inputs used
merged_prs104
open_issues9
closed_issues25
prs_merged_7d0
prs_decided_7d1
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.735
closed_unmerged_prs4
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
6.1/25Owner reach6 followers of xxsds
16.4/25Track record3 public repos, account ~10 yr old
Inputs used
followers6
owner_typeOrganization
is_verifiedno
owner_loginxxsds
public_repos3
account_age_days3,854

Engineering Quality

Are baseline engineering and documentation practices in place?

41Weak · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests7 out of 10 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

10Critical
How it's scored
0/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
10/10Topics14 topics
0/10Wiki
Inputs used
topicscpp14, cpp-library, data-structures, template-library, succint-data-structure, compressed-suffix-trees, fm-index, wavelet-tree, bitvector, indexing, lcp-array, suffixarray, cpp17, cpp20
has_wikino
homepage
docs_site
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

49Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
1.8/2.5CI-Tests7 out of 10 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
1.5/7.5Code-ReviewFound 1/5 approved changesets -- score normalized to 2
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.2/2.5Licenselicense file detected
2.2/7.5Maintained3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.9
Excluded from scoring (no data or not applicable): 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.

62Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
30.3/40Legible commit history50 of 88 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.568
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapbenchmark/document_retrieval/Makefile, benchmark/document_retrieval/visualize/Makefile, benchmark/indexing_count/Makefile, benchmark/indexing_count/visualize/Makefile, benchmark/indexing_extract/Makefile, benchmark/indexing_extract/visualize/Makefile, benchmark/indexing_locate/Makefile, benchmark/indexing_locate/visualize/Makefile, benchmark/k2_trees/Makefile, benchmark/k2_trees/visualize/Makefile, benchmark/lcp/Makefile, benchmark/lcp/visualize/Makefile, benchmark/rrr_vector/Makefile, benchmark/rrr_vector/visualize/Makefile, benchmark/self_delimiting_codes/Makefile, benchmark/self_delimiting_codes/visualize/Makefile, benchmark/suffix_trees/Makefile, benchmark/suffix_trees/visualize/Makefile, benchmark/wavelet_trees/Makefile, benchmark/wavelet_trees/visualize/Makefile, extras/cheatsheet/Makefile, tutorial/document_listing/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checkingC++ (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance12 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_filesbenchmark/document_retrieval/Makefile, benchmark/document_retrieval/visualize/Makefile, benchmark/indexing_count/Makefile, benchmark/indexing_count/visualize/Makefile, benchmark/indexing_extract/Makefile, benchmark/indexing_extract/visualize/Makefile, benchmark/indexing_locate/Makefile, benchmark/indexing_locate/visualize/Makefile, benchmark/k2_trees/Makefile, benchmark/k2_trees/visualize/Makefile, benchmark/lcp/Makefile, benchmark/lcp/visualize/Makefile, benchmark/rrr_vector/Makefile, benchmark/rrr_vector/visualize/Makefile, benchmark/self_delimiting_codes/Makefile, benchmark/self_delimiting_codes/visualize/Makefile, benchmark/suffix_trees/Makefile, benchmark/suffix_trees/visualize/Makefile, benchmark/wavelet_trees/Makefile, benchmark/wavelet_trees/visualize/Makefile, extras/cheatsheet/Makefile, tutorial/document_listing/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.12
How it's scored
45/45Type-checkable codeC++ (statically typed)
54.2/55Manageable file sizes4/259 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes151,125
source_files_sampled259
oversized_source_files4
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

110GitHub stars
41contributors
19commits, last 12 months
80days since last push
5releases
1bus factor
9open issues
package ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Community profile unavailable

More detail

Star and fork history 0 ★ / 18 ⇿
0Stars
18Forks
4Releases

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.

0481216201822017-032021-092026-03
Major 1Minor 0Patch 3

Each point covers 9 days.

OpenSSF Scorecard 4.9 / 10
4.9aggregate

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-09-20 07:09 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
7CI-Tests7 out of 10 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 1/5 approved changesets -- score normalized to 2
10Contributorsproject has 11 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
3Maintained3 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 3
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
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

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.