qiskit/ecosystem

0

/ 100

Documentation76
Engineering85
Health100
Python154Apache-2.01d ago
Grade a repo

Polished and well engineered. Punching above its star count.

The Qiskit ecosystem is a collection of tools created by researchers and developers who use Qiskit every day.

Documentation

76

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

Contributing guide5pt83

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt85

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

85

Reproducibility6pt70

Lockfile present (requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (ecosystem/validation/conftest.py).

CI/CD14pt85

CI is configured (.github/workflows/tests.yml).

Linting and formatting5pt100

Linter or formatter configured (.pylintrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 89
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 154
    Watchers

Responsiveness

  • 9d 1h
    Median issue response
  • 11h
    Median PR merge time
  • 9
    Open issues
Repository files19 root entries
  • .github
    Good: CI is configured (.github/workflows/tests.yml).
    Good: Issue or PR templates present.
  • docs
  • ecosystem
    Good: Test files detected (ecosystem/validation/conftest.py).
  • resources
  • tests
  • .coveragerc
  • .gitignore
    Good: .gitignore present.
  • .pylintrc
    Good: Linter or formatter configured (.pylintrc).
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • manager.py
  • mkdocs.yml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • requirements-dev.txt
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • setup.cfg
  • setup.py
  • tox.ini