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

applicable weight 65%

danila-kurenev/codlauncher

Language: Python
branch main

Приложение CodLauncher

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 22:23 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 practicessignal coverage 95%
15.8–17.2 / 30.8
partial
Project activity
19.9 / 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: contributing guide, 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
  • CI checks pull requests
  • Commits span the whole year (296 commits)
  • Contributions are spread across authors
  • A team works on the project (5 authors)

What affected the score

Penalties

Documentation and best practices

  • −6
    README38 chars, no quickstart
  • −3
    license filemissing
  • −3
    dependency lockfilemissing
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 4%

Project activity

  • −4
    last releaseno releases or version tags
  • −4
    share of unanswered pull requests — 100%sample: 5 of 10
  • −2
    share of closed pull requests — 38%window: 50 PRs, sample threshold: 5 of 10
  • −1
    weekly activity — 5 weeks
  • −<1
    last commit — 50 days

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 −1
    contributing guidedata not collected

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
  • Documentation
    +6
    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
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Activity
    +4
    respond to pull requestsshare of unanswered pull requests — 100%why: an outside contributor gets an answer, and their work is not lostevidence: the repository's pull request list, snapshot of 8 October 2026
  • add a license file+3
  • add a dependency lockfile+3
  • close pull requests+2
  • set up a branch protection policy+1
  • spread work across more weeks instead of bursts+1
  • make a commit soon+<1
  • write meaningful commit messages+<1