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

applicable weight 80%

lct-hackaton-2026/case-17-vehicle-digital-signature-team-14

Language: Jupyter Notebook
branch main

ЛЦТ 2026 · Кейс 17 · Команда 14 — Цифровой признак транспортного средства для сопоставления снимков

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 29 September 2026 at 21:57 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
17.8 / 25
scored
Project activity
19.5 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
18.3 / 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 (9 days)
  • Almost no marked debt in the code
  • The README introduces the project
  • Issues are closed quickly (today)
  • Commits are fresh (9 days)

What affected the score

Penalties

Documentation and best practices

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

Project activity

  • −4
    last releaseno releases or version tags
  • −1
    weekly activity — 3 weeks

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −<1
    issue resolution time — today6 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 −9
    CI runsdata not collected

What will raise the score

by strength of impact
  • CI/CD
    +9
    add a SourceCraft CI configuration (.sourcecraft/ci.yaml); the service does not see external CISourceCraft CI configurationwhy: the build and the checks are reproducible for whoever takes the code
  • Activity
    +4
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Documentation
    +2
    add a license filelicense filewhy: the terms of use are stated, not guessed
  • set up a review policy+2
  • spread work across more weeks instead of bursts+1
  • add a contributing guide+1
  • set up a branch protection policy+1
  • close issues faster+<1
  • write meaningful commit messages+<1