Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 19:46 UTC

quantumlib / Stim

A fast stabilizer circuit library.

C++ · Jupyter Notebook · PythonApache-2.0★ 835 stars⑂ 242 forkssince Feb 2021View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

quantumlib/Stim holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (82/100) and lowest on AI Readiness (64/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

QuantumlibOrganization
1,448 followers17 public repossince Aug 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIstim1.16.0282,186127150 days ago—
npmstimpoints to another repo — not scored1.22.012,114311 day agoagentemulatorexpometroreact-nativesimulatorworktree

Metrics by category

Vitality

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

71Good · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
13.2/36Commit cadence — 19/52 weeks with commits
15.7/18Commit volume — 55 commits in the last year
9/10OpenSSF Scorecard: Maintained — 6 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year55
human_commit_share0.97
days_since_last_push3
active_weeks_last_year19
How it's scored
27/27Ships releases — 20 releases published
27/36Release recency — latest release 150 days ago
12.6/27Release cadence — a release every ~174.8 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count20
latest_release_tagv1.16.0
releases_from_tagsno
days_since_latest_release150
mean_days_between_releases174.8

Community & Adoption

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

82Excellent · 17% of overall
How it's scored
47.4/60Stars — 835 stars
19.9/25Forks — 242 forks
6.5/15Watchers — 16 watchers
Inputs used
forks242
stars835
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
72.7/80Monthly downloads — 282,186 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesstim
dependents—
ecosystemspypi
total_downloads—
monthly_downloads282,186
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?

68Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.3/22.5Commit distribution — top contributor authored 85% of commits
13.5/13.5Contributor breadth — 42 contributors
10/10OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled42
top_contributor_share0.852
How it's scored
35.2/42Issue resolution — 84% of issues closed
26.5/30PR acceptance — 559/633 decided PRs merged
9.8/13Newcomer PR acceptance — 3/4 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 9/30 approved changesets -- score normalized to 3
Inputs used
merged_prs559
open_issues75
closed_issues390
prs_merged_7d2
prs_decided_7d2
prs_merged_30d4
prs_decided_30d5
issue_closed_ratio0.839
closed_unmerged_prs74
first_time_authors_30d4
first_time_prs_merged_30d3
first_time_prs_decided_30d4
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
22.7/25Owner reach — 1,448 followers of quantumlib
21.1/25Track record — 17 public repos, account ~9 yr old
Inputs used
followers1,448
owner_typeOrganization
is_verifiedno
owner_loginquantumlib
public_repos17
account_age_days3,344

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 150 days ago
20/20Version history — 127 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesstim
ecosystemspypi
any_deprecatedno
min_days_since_publish150

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 2 topics
10/10Wiki
Inputs used
topicsquantum-computing, stabilizer-circuits
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

64Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 9/30 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 12 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
6.8/7.5Maintained — 6 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 9
5/5Packaging — packaging workflow detected
2.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file 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
0/7.5Vulnerabilities — 11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.5
Excluded from scoring (no data or not applicable): Branch-Protection. 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_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 pypi:stim@1.16.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.

64Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 91 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.938
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C++ (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 3 of the last 100 commits are automated dependency updates
5/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.03
How it's scored
45/45Type-checkable code — C++ (statically typed)
53.9/55Manageable file sizes — 15/727 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes225,886
source_files_sampled727
oversized_source_files15
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — notebooks, sample
Inputs used
example_dirsnotebooks, sample
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

835GitHub stars
42contributors
55commits, last 12 months
3days since last push
20releases
1bus factor
75open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'stim' points at a different repository (https://github.com/appandflow/stim); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 242 ⇿
0Stars
242Forks
19Releases

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.

05010015020025024242021-032023-122026-10
Major 0Minor 16Patch 3

Each point covers 6 days.

OpenSSF Scorecard 5.5 / 10
5.5aggregate

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-10-19 19:46 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-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 9/30 approved changesets -- score normalized to 3
10Contributorsproject has 12 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
9Maintained6 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 9
10Packagingpackaging workflow detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities11 existing vulnerabilities detected
All dependencies 71

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

RegistryPackageVersionRelation
npm@types/node22.15.17indirect
npm@types/yauzl2.10.3indirect
npmagent-base5.1.1indirect
npmbalanced-match1.0.2indirect
npmbase64-js1.5.1indirect
npmbl4.1.0indirect
npmbrace-expansion1.1.11indirect
npmbuffer5.7.1indirect
npmbuffer-crc320.2.13indirect
npmchownr1.1.4indirect
npmconcat-map0.0.1indirect
npmdebug4.4.0indirect
npmdevtools-protocol0.0.818844indirect
npmend-of-stream1.4.4indirect
npmextract-zip2.0.1indirect
npmfd-slicer1.1.0indirect
npmfind-up4.1.0indirect
npmfs-constants1.0.0indirect
npmfs.realpath1.0.0indirect
npmget-stream5.2.0indirect
npmglob7.2.3indirect
npmhttps-proxy-agent4.0.0indirect
npmieee7541.2.1indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmlocate-path5.0.0indirect
npmminimatch3.1.5indirect
npmmkdirp-classic0.5.3indirect
npmms2.1.3indirect
npmnode-fetch2.7.0indirect
npmonce1.4.0indirect
npmp-limit2.3.0indirect
npmp-locate4.1.0indirect
npmp-try2.2.0indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpend1.2.0indirect
npmpkg-dir4.2.0indirect
npmprogress2.0.3indirect
npmproxy-from-env1.1.0indirect
npmpump3.0.2indirect
npmpuppeteer5.5.0indirect
npmreadable-stream3.6.2indirect
npmrimraf3.0.2indirect
npmsafe-buffer5.2.1indirect
npmstring_decoder1.3.0indirect
npmtar-fs2.1.4indirect
npmtar-stream2.2.0indirect
npmthrough2.3.8indirect
npmtr460.0.3indirect
npmunbzip2-stream1.4.3indirect
npmundici-types6.21.0indirect
npmutil-deprecate1.0.2indirect
npmwebidl-conversions3.0.1indirect
npmwhatwg-url5.0.0indirect
npmwrappy1.0.2indirect
npmws7.5.10indirect
npmyauzl2.10.0indirect
PyPIcirq-core—indirect
PyPIipykernel—indirect
PyPImatplotlib—indirect
PyPInetworkx—indirect
PyPInumpy—indirect
PyPIpybind11—indirect
PyPIpygltflib—indirect
PyPIpymatching—indirect
PyPIpytest—indirect
PyPIpython3-distutils—indirect
PyPIscipy—indirect
PyPIstim—indirect
PyPIz3-solver4.12.1.0indirect
Dependency advisories 0

Installing pypi:stim@1.16.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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — PyPI, npm.