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

applicable weight 80%

ivanbindusov/simple-rtos

Language: C
branch main
mirror
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 18:52 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
9.7 / 25
scored
Project activity
11.5 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
16.4 / 18.8
scored
Code health
12.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
  • Almost no marked debt in the code
  • The README introduces the project
  • Commits span the whole year (38 commits)
  • Commits are fresh (62 days)
  • Commit messages are meaningful

What affected the score

Penalties

Documentation and best practices

  • −3
    license filemissing
  • −3
    tests directorymissing
  • −3
    docs directorymissing
  • −3
    Dockerfilemissing
  • −3
    dependency lockfilemissing
  • −1
    contributing guidemissing
  • −<1
    share of short commit messages — 3%

Project activity

  • −4
    top author's share of commits — 100%
  • −4
    unique authors — 1 author
  • −4
    last releaseno releases or version tags
  • −1
    weekly activity — 5 weeks
  • −<1
    last commit — 62 days

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −2
    age of open issues — 75 days1 issue

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
  • 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
  • Activity
    +4
    share the work with other contributorstop author's share of commits — 100%why: the work does not rest on a single person
  • Activity
    +4
    bring in a second maintainerunique authors — 1 authorwhy: the work does not rest on a single person
  • publish a release or tag a version+4
  • add a license file+3
  • write tests for the project+3
  • write project documentation+3
  • containerize the project — add a Dockerfile+3
  • add a dependency lockfile+3
  • work through the stale open issues+2
  • add a contributing guide+1
  • spread work across more weeks instead of bursts+1
  • make a commit soon+<1
  • write meaningful commit messages+<1