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

applicable weight 55%

helmci/ci

Language: Makefile
branch main

This is a core module for managing the entire company infrastructure using nested system, application, and project modules. Each module includes all dependent modules via Git submodules or symlinks and can be used independently of the parent.

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

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; Code health. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practices
14.6 / 36.4
scored
Project activity
0 / 36.4
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–13.6 / 27.3
partial
Issuesthe tracker is empty or not set up
no data
Code health
no data
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
  • The license file is in place
  • Tests live in the repository

What affected the score

Penalties

Documentation and best practices

  • −4
    README4,204 chars, no quickstart
  • −3
    docs directorymissing
  • −3
    Dockerfilemissing
  • −3
    dependency lockfilemissing
  • −3
    review policyno protection
  • −2
    contributing guidemissing
  • −2
    branch protection policyno protection
  • −<1
    share of short commit messages — 19%

Project activity

  • −6
    last commit — 591 days
  • −6
    commits in the last year — 0 commits
  • −6
    weekly activity — 0 weeks
  • −6
    top author's share of commits — 100%
  • −6
    unique authors — 1 author
  • −6
    last releaseno releases or version tags

CI/CD

  • −14
    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

CI/CD

  • up to −14
    CI runsdata not collected

What will raise the score

by strength of impact
  • CI/CD
    +14
    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
    +6
    make a commit soonlast commit — 591 dayswhy: the repository shows it is alive, not abandoned
  • Activity
    +6
    commit more oftencommits in the last year — 0 commitswhy: the repository shows it is alive, not abandoned
  • spread work across more weeks instead of bursts+6
  • share the work with other contributors+6
  • bring in a second maintainer+6
  • publish a release or tag a version+6
  • add a quickstart section to the README+4
  • write project documentation+3
  • containerize the project — add a Dockerfile+3
  • add a dependency lockfile+3
  • set up a review policy+3
  • add a contributing guide+2
  • set up a branch protection policy+2
  • write meaningful commit messages+<1