Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 10:49 UTC

ashvardanian / StringZilla

Up to 100x faster strings for C, C++, CUDA, Python, Rust, Swift, JS, & Go, leveraging NEON, AVX2, AVX-512, SVE, GPGPU, & SWAR to accelerate search, hashing, sorting, edit distances, sketches, and memory ops 🦖

C · C++Apache-2.0★ 3,555 stars⑂ 135 forkssince Aug 2020View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

ashvardanian/StringZilla holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (85/100) and lowest on Security (54/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Ash VardanianPersonal account
1,446 followers61 public repossince Jul 2012BDFL @ Unum

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 publishTags
crates.iostringzilla5.1.22,1069931 days agohashretrievalsearchsimdsortno-stdhardware-supporttext-processingwasm
npmstringzilla5.1.23853931 days agosimdsearchstringperformancehashsortgpucudafuzzy-searchnative-addon
Gogithub.com/ashvardanian/StringZillav5.1.2+incompatible-11831 days ago—

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
17.3/36Commit cadence — 25/52 weeks with commits
18/18Commit volume — 928 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year928
human_commit_share1
days_since_last_push4
active_weeks_last_year25
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 31 days ago
27/27Release cadence — a release every ~2.4 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv5.1.2
releases_from_tagsno
days_since_latest_release31
mean_days_between_releases2.4

Community & Adoption

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

72Good · 17% of overall
How it's scored
57.6/60Stars — 3,555 stars
17.7/25Forks — 135 forks
7.8/15Watchers — 26 watchers
Inputs used
forks135
stars3,555
watchers26
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
45.3/80Monthly downloads — 2,491 downloads/month across crates, go, npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesstringzilla, stringzilla, github.com/ashvardanian/StringZilla
dependents—
ecosystemscrates, go, npm
total_downloads101,592
monthly_downloads2,491
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.5/22.5Commit distribution — top contributor authored 93% of commits
13.5/13.5Contributor breadth — 40 contributors
10/10OpenSSF Scorecard: Contributors — project has 13 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled40
top_contributor_share0.933
How it's scored
34.9/42Issue resolution — 83% of issues closed
25.6/30PR acceptance — 164/192 decided PRs merged
0/13Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 3/13 approved changesets -- score normalized to 2
Inputs used
merged_prs164
open_issues24
closed_issues117
prs_merged_7d0
prs_decided_7d1
prs_merged_30d0
prs_decided_30d2
issue_closed_ratio0.83
closed_unmerged_prs28
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
22.7/25Owner reach — 1,446 followers of ashvardanian
25/25Track record — 61 public repos, account ~14 yr old
Inputs used
followers1,446
owner_typeUser
is_verified—
owner_loginashvardanian
public_repos61
account_age_days5,171
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 3 package(s) on crates, go, npm
35/35Publish recency — latest publish 31 days ago
20/20Version history — 118 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesstringzilla, stringzilla, github.com/ashvardanian/StringZilla
ecosystemscrates, go, npm
any_deprecatedno
min_days_since_publish31

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.json, Cargo.toml ([lints]), pyproject.toml ([tool.ruff], [tool.black]), rustfmt.toml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests — 2 out of 5 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://ashvardanian.com/posts/stringzilla/
10/10Repository description
10/10Topics — 18 topics
0/10Wiki
Inputs used
topicssimd, dataset, string, string-manipulation, string-matching, substring, information-retrieval, sorting-algorithms, string-parsing, string-search, parser, hash, hashing, levenshtein-distance, edit-distance, gpu, search, unicode
has_wikino
homepagehttps://ashvardanian.com/posts/stringzilla/
docs_sitehttps://ashvardanian.com/posts/stringzilla/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1/2.5CI-Tests — 2 out of 5 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 3/13 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 13 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages6
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 crates:stringzilla@5.1.2 runtime dependency closure — what installing the published package pulls in — 6 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.

67Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://ashvardanian.com/llms.txt)
40/40Legible commit history — 99 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://ashvardanian.com/llms.txt
legible_history_share0.99
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml, StringZilla.csproj, csharp/StringZillaTests.csproj (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — .eslintrc.json, Cargo.toml ([lints]), pyproject.toml ([tool.ruff], [tool.black]), rustfmt.toml
11/11Static type checking — C (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, StringZilla.csproj, csharp/StringZillaTests.csproj, golang/go.mod, pom.xml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C (statically typed)
48.1/55Manageable file sizes — 46/367 source files over 60KB
Inputs used
primary_languageC
largest_source_bytes504,419
source_files_sampled367
oversized_source_files46

Key facts

3,555GitHub stars
40contributors
928commits, last 12 months
4days since last push
100releases
1bus factor
24open issues
crates.io, Go, Maven, npm, NuGet, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-17: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 3555 stars today.
  • Could not fetch maven package 'com.github.ashvardanian:stringzilla' from its registry
  • Could not fetch nuget package 'StringZilla' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 3,515 ★ / 135 ⇿
3,515Stars
135Forks
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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-17. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

01,2502,5003,7503,5151332432021-102024-032026-09
Major 2Minor 18Patch 80

Each point covers 5 days.

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-09-12 10:48 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
4CI-Tests2 out of 5 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 3/13 approved changesets -- score normalized to 2
10Contributorsproject has 13 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 20 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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
crates.ioallocator-api20.4Cargo.toml
crates.ioforkunion3.0Cargo.toml
crates.iostringtape2.4.2Cargo.toml
NuGetMicrosoft.NET.Test.Sdk18.7.0csharp/StringZillaTests.csproj
NuGetxunit2.9.3csharp/StringZillaTests.csproj
NuGetxunit.runner.visualstudio3.1.5csharp/StringZillaTests.csproj
npmbindings^1.5.0package.json
npmnode-addon-api^8.0.0package.json
npmnode-gyp-build^4.8.4package.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

Dependency advisories 0

Installing crates:stringzilla@5.1.2 pulls in 6 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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — crates.io, npm, Go.