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

applicable weight 80%

12345/sekretimoi

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 18:59 UTC — part unavailable

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
0–25 / 25
collection failed
Project activity
0 / 25
scored
Securitywill appear with a member token
no data
CI/CD
0–18.8 / 18.8
collection failed
Issues
0.8 / 18.8
scored
Code health
0–12.5 / 12.5
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: README, license file, tests directory, docs directory, Dockerfile, dependency lockfile, contributing guide, branch protection policy, review policy, SourceCraft CI configuration, CI configuration contents, TODO/FIXME density
data not collected
the surface didn't answer this collection run

Strengths

what's already done

No metric has a full score yet

What affected the score

Penalties

Project activity

  • −8
    commits in the last year — 0 commits
  • −8
    weekly activity — 0 weeks
  • −8
    last releaseno releases or version tags

Issues

  • −18
    age of open issues — 519 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

Documentation and best practices

  • up to −8
    READMEdata not collected
  • up to −3
    license filedata not collected
  • up to −3
    tests directorydata not collected
  • up to −3
    docs directorydata not collected
  • up to −3
    Dockerfiledata not collected
  • up to −3
    dependency lockfiledata not collected
  • up to −3
    review policydata not collected
  • up to −1
    contributing guidedata not collected
  • up to −1
    branch protection policydata not collected

CI/CD

  • up to −8
    SourceCraft CI configurationdata not collected
  • up to −8
    CI runsdata not collected
  • up to −4
    CI configuration contentsdata not collected

Code health

  • up to −13
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • Issues
    +18
    work through the stale open issuesage of open issues — 519 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • Activity
    +8
    commit more oftencommits in the last year — 0 commitswhy: the repository shows it is alive, not abandoned
  • Activity
    +8
    spread work across more weeks instead of burstsweekly activity — 0 weekswhy: the repository shows it is alive, not abandoned
  • publish a release or tag a version+8