Skip to the main content
The Repo Vitals mark: a pulse that ends in a commitREPO VITALS

applicable weight 80%

otekotak/httpx

Language: Python
branch master
imported from GitHub

A next generation HTTP client for Python. 🦋

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 21:25 UTC — part unavailable

What the 100 is made of

category weight
Documentation 20Activity 20Security 20CI/CD 15Issues 15Code health 10

The light segment — Security: will appear with a member token, while the rest share its weight for now.

Six categories

earned / weight
Documentation and best practicessignal coverage 90%
16.6–19 / 25
partial
Project activitysignal coverage 83%
15.7–19.9 / 25
partial
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
8 / 18.8
scored
Code health
0–12.5 / 12.5
collection failed
States:
scored
partial
no data
weight goes to the rest
collection failed
interval, not zero
Not measured: CI runs
closed by the platform
will become a group once access opens
Not measured: Dockerfile, last release, TODO/FIXME density
couldn't see it
the platform's window was truncated: a deep file or a recent version may have fallen outside it

Strengths

what's already done
  • The README introduces the project
  • A team works on the project (5 authors)
  • Issues are closed quickly (today)
  • The license file is in place
  • Tests live in the repository

What affected the score

Penalties

Documentation and best practices

  • −2
    dependency lockfilemissing
  • −2
    review policyno protection
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 6%

Project activity

  • −2
    last commit — 207 days
  • −1
    top author's share of commits — 71%
  • −1
    weekly activity — 4 weeks
  • −1
    commits in the last year — 14 commits

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −8
    share of unanswered issues — 100%sample: 6 of 10
  • −3
    age of open issues — 207 days9 issues

Not measured — interval width

Not a penalty: the lower bound of the score counts the metric as zero, the upper bound as full

Documentation and best practices

  • up to −2
    Dockerfiledata not collected

Project activity

  • up to −4
    last releasedata not collected

CI/CD

  • up to −9
    CI runsdata not collected

Code health

  • up to −13
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • CI/CD
    +9
    add a SourceCraft CI configuration (.sourcecraft/ci.yaml); the service does not see external CISourceCraft CI configurationwhy: the build and the checks are reproducible for whoever takes the code
  • Issues
    +8
    respond to issuesshare of unanswered issues — 100%why: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • Issues
    +3
    work through the stale open issuesage of open issues — 207 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • add a dependency lockfile+2
  • set up a review policy+2
  • make a commit soon+2
  • share the work with other contributors+1
  • set up a branch protection policy+1
  • spread work across more weeks instead of bursts+1
  • commit more often+1
  • write meaningful commit messages+<1