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

applicable weight 65%

smart-lyceum/cogni-vault

Language: Python
branch master
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 22:35 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 practices
23.4 / 30.8
scored
Project activity
25.2 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
13.8–23.1 / 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: 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
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits span the whole year (130 commits)
  • Contributions are spread across authors
  • A team works on the project (4 authors)

What affected the score

Penalties

Documentation and best practices

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

Project activity

  • −3
    last release — 231 days
  • −2
    weekly activity — 3 weeks
  • −1
    last commit — 84 days

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

Code health

  • up to −15
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • Activity
    +3
    publish a release or tag a versionlast release — 231 dayswhy: the build and the checks are reproducible for whoever takes the code
  • Documentation
    +3
    add a dependency lockfiledependency lockfilewhy: the build and the checks are reproducible for whoever takes the code
  • Documentation
    +3
    set up a review policyreview policywhy: a change is reviewed, and the history stays readable
  • spread work across more weeks instead of bursts+2
  • set up a branch protection policy+1
  • make a commit soon+1