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

applicable weight 80%

maxprodoma/kvae-stack

Language: HTML
branch main

KVAE-Audio API, AI-Трекер задач, мониторинг и документация стека

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 22:28 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
5.8 / 25
scored
Project activity
7.3 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.3–18.8 / 18.8
partial
Issues
7.7 / 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
  • SourceCraft CI is configured
  • CI checks pull requests
  • The main branch is protected

What affected the score

Penalties

Documentation and best practices

  • −5
    README79 chars, no quickstart
  • −2
    license filemissing
  • −2
    tests directorymissing
  • −2
    docs directorymissing
  • −2
    Dockerfilemissing
  • −2
    dependency lockfilemissing
  • −1
    contributing guidemissing
  • −1
    review policybasic protection
  • −<1
    share of short commit messages — 17%

Project activity

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

Issues

  • −9
    share of unanswered issues — 100%sample: 7 of 10
  • −2
    age of open issues — 94 days7 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
  • Issues
    +9
    respond to issuesshare of unanswered issues — 100%why: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • Documentation
    +5
    add a quickstart section to the READMEREADMEwhy: a newcomer can tell how to run the project and where to lookevidence: file README.md, snapshot of 8 October 2026
  • Activity
    +4
    share the work with other contributorstop author's share of commits — 100%why: the work does not rest on a single person
  • bring in a second maintainer+4
  • publish a release or tag a version+4
  • spread work across more weeks instead of bursts+3
  • add a license file+2
  • write tests for the project+2
  • write project documentation+2
  • containerize the project — add a Dockerfile+2
  • add a dependency lockfile+2
  • work through the stale open issues+2
  • commit more often+1
  • add a contributing guide+1
  • set up a review policy+1
  • make a commit soon+1
  • write meaningful commit messages+<1