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

applicable weight 80%

wolf/speedy

Language: Python
branch dev_2_0
imported from GitHub

In development

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 18:49 UTC — not all categories measured

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 practices
10.4 / 25
scored
Project activity
16.6 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
10.4 / 18.8
scored
Code health
1.5 / 12.5
scored
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

Strengths

what's already done
  • Commits span the whole year (310 commits)
  • Work goes on without long pauses (20 weeks)
  • A team works on the project (4 authors)
  • The license file is in place
  • Tests live in the repository

What affected the score

Penalties

Documentation and best practices

  • −5
    README73 chars, no quickstart
  • −2
    docs directorymissing
  • −2
    Dockerfilemissing
  • −2
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 10%

Project activity

  • −4
    last releaseno releases or version tags
  • −3
    top author's share of commits — 90%
  • −1
    last commit — 143 days

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −4
    issue resolution time — 33 days7 issues
  • −4
    age of open issues — 161 days7 issues

Code health

  • −11
    TODO/FIXME density

Not measured — interval width

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

CI/CD

  • up to −9
    CI runsdata not collected

What will raise the score

by strength of impact
  • Code health
    +11
    work through the TODO/FIXME marks in the codeTODO/FIXME densitywhy: the code stays workable: marked debt does not pile up
  • 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
  • Documentation
    +5
    add a quickstart section to the READMEREADMEwhy: a newcomer can tell how to run the project and where to lookevidence: file README.md, snapshot of 8 October 2026
  • close issues faster+4
  • work through the stale open issues+4
  • publish a release or tag a version+4
  • share the work with other contributors+3
  • write project documentation+2
  • containerize the project — add a Dockerfile+2
  • set up a review policy+2
  • make a commit soon+1
  • add a contributing guide+1
  • set up a branch protection policy+1
  • write meaningful commit messages+<1