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

applicable weight 65%

lct-hackaton-2026/case12-re-pcb-39

Language: Python
branch main
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 29 September 2026 at 22:56 UTC — part unavailable

What the 100 is made of

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

The light segments — Security: will appear with a member token; Issues: the tracker is empty or not set up. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practicessignal coverage 76%
13.2–20.5 / 30.8
partial
Project activity
9.7 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–11.5 / 23.1
partial
Issuesthe tracker is empty or not set up
no data
Code health
0–15.4 / 15.4
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: tests directory, Dockerfile, contributing guide, 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
  • Commits are fresh (9 days)
  • Documentation has its own directory
  • Commit messages are meaningful

What affected the score

Penalties

Documentation and best practices

  • −3
    license filemissing
  • −3
    dependency lockfilemissing
  • −3
    review policyno protection
  • −1
    branch protection policyno protection

Project activity

  • −5
    top author's share of commits — 100%
  • −5
    unique authors — 1 author
  • −5
    last releaseno releases or version tags
  • −4
    weekly activity — 1 week
  • −2
    commits in the last year — 5 commits

CI/CD

  • −12
    SourceCraft CI configurationmissing

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 −3
    tests directorydata not collected
  • up to −3
    Dockerfiledata not collected
  • up to −1
    contributing guidedata not collected

CI/CD

  • up to −12
    CI runsdata not collected

Code health

  • up to −15
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • CI/CD
    +12
    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
  • Activity
    +5
    share the work with other contributorstop author's share of commits — 100%why: the work does not rest on a single person
  • Activity
    +5
    bring in a second maintainerunique authors — 1 authorwhy: the work does not rest on a single person
  • publish a release or tag a version+5
  • spread work across more weeks instead of bursts+4
  • add a license file+3
  • add a dependency lockfile+3
  • set up a review policy+3
  • commit more often+2
  • set up a branch protection policy+1