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

applicable weight 80%

raph/honk

Language: Shell
branch master

Плагин для Claude Code и Codex, который помогает превратить продуктовую задачу в структурированный Feature Brief

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 18:41 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
10.7 / 25
scored
Project activity
24.6 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
9.8–17.3 / 18.8
partial
Issues
18.2 / 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
  • Open issues do not pile up (41 days)
  • Almost no marked debt in the code
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (29 days)

What affected the score

Penalties

Documentation and best practices

  • −2
    license filemissing
  • −2
    tests directorymissing
  • −2
    Dockerfilemissing
  • −2
    dependency lockfilemissing
  • −2
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 4%

Project activity

  • −<1
    top author's share of commits — 55%

CI/CD

  • −2
    CI configuration contents

Issues

  • −1
    age of open issues — 41 days2 issues

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 −8
    CI runsdata not collected

What will raise the score

by strength of impact
  • Documentation
    +2
    add a license filelicense filewhy: the terms of use are stated, not guessed
  • Documentation
    +2
    write tests for the projecttests directorywhy: the build and the checks are reproducible for whoever takes the code
  • Documentation
    +2
    containerize the project — add a DockerfileDockerfilewhy: a newcomer can tell how to run the project and where to look
  • add a dependency lockfile+2
  • set up a review policy+2
  • run CI on pull requests, not only on pushes to the default branch+2
  • add a contributing guide+1
  • set up a branch protection policy+1
  • work through the stale open issues+1
  • share the work with other contributors+<1
  • write meaningful commit messages+<1