Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 10:45 UTC

Qiskit / qiskit-qasm3-import

Importer from OpenQASM 3 to Qiskit's QuantumCircuit

PythonApache-2.0★ 27 stars⑂ 9 forkssince Nov 2022View on GitHub ↗

Qiskit/qiskit-qasm3-import holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (89/100) and lowest on Vitality (35/100). It was last updated 119 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

QiskitOrganization
4,157 followers65 public repossince Aug 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIqiskit-qasm3-import0.6.0510,89210524 days ago

Metrics by category

Vitality

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

35Weak · 21% of overall
How it's scored
9.9/36Push recency — last push 119 days ago
2.8/36Commit cadence — 4/52 weeks with commits
9/18Commit volume — 9 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year9
human_commit_share0.729
days_since_last_push119
active_weeks_last_year4
How it's scored
27/27Ships releases — 7 releases published
0/36Release recency — latest release 881 days ago
19.8/27Release cadence — a release every ~97.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tagv0.5.0
releases_from_tagsno
days_since_latest_release881
mean_days_between_releases97.8

Community & Adoption

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

68Good · 17% of overall
How it's scored
23/60Stars — 27 stars
7.5/25Forks — 9 forks
5.3/15Watchers — 10 watchers
Inputs used
forks9
stars27
watchers10
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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
76.1/80Monthly downloads — 510,892 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesqiskit-qasm3-import
dependents—
ecosystemspypi
total_downloads—
monthly_downloads510,892
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.7/22.5Commit distribution — top contributor authored 84% of commits
6.8/13.5Contributor breadth — 5 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.837
How it's scored
18.6/42Issue resolution — 44% of issues closed
30/30PR acceptance — 46/46 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs46
open_issues10
closed_issues8
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.444
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
25/25Owner reach — 4,157 followers of Qiskit
25/25Track record — 65 public repos, account ~9 yr old
Inputs used
followers4,157
owner_typeOrganization
is_verifiedno
owner_loginQiskit
public_repos65
account_age_days3,392
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
14/35Publish recency — latest publish 524 days ago
20/20Version history — 10 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesqiskit-qasm3-import
ecosystemspypi
any_deprecatedno
min_days_since_publish524

Engineering Quality

Are baseline engineering and documentation practices in place?

89Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.pylint], [tool.black]), tox.ini
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://qiskit.github.io/qiskit-qasm3-import
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsopenqasm, qiskit, quantum-computing
has_wikino
homepagehttps://qiskit.github.io/qiskit-qasm3-import
docs_sitehttps://qiskit.github.io/qiskit-qasm3-import
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

46Weak · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestspyproject.toml, requirements-dev.txt, setup.cfg
has_codeql_workflowno
has_security_policyno
has_dependabot_configyes
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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_packages9
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:qiskit-qasm3-import@0.6.0 runtime dependency closure — what installing the published package pulls in — 9 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.

65Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
39.7/40Legible commit history — 32 of 43 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.744
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.pylint], [tool.black]), tox.ini
11/11Static type checking — src/qiskit_qasm3_import/py.typed
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 59
8/8Automated maintenance — 16 of the last 59 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/qiskit_qasm3_import/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.271
How it's scored
27/45Type-checkable code — Python with type-check config (src/qiskit_qasm3_import/py.typed)
55/55Manageable file sizes — 0/13 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes33,697
source_files_sampled13
oversized_source_files0

Key facts

27GitHub stars
5contributors
9commits, last 12 months
119days since last push
7releases
1bus factor
10open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 0 ★ / 9 ⇿
0Stars
9Forks
6Releases

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.

0246810912022-112023-122025-01
Major 0Minor 4Patch 2

Each point covers 2 days.

Direct dependencies 2
RegistryPackageVersion constraintManifest
PyPIqiskit>=0.37.0setup.cfg
PyPIopenqasm3>=0.4,<2.0setup.cfg
All dependencies 7

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

RegistryPackageVersionRelation
PyPIblack—indirect
PyPIpackaging—indirect
PyPIpylint—indirect
PyPIpytest—indirect
PyPIqiskit-sphinx-theme—indirect
PyPIreno—indirect
PyPIsphinx—indirect
Dependency advisories 0

Installing pypi:qiskit-qasm3-import@0.6.0 pulls in 9 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.