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

applicable weight 65%

lct-hackaton-2026/case-15-uav-flight-planning-team-58

Language: Python
branch main

ЛЦТ 2026 · Кейс 15 · Команда 58 — Планирование и распределение беспилотных авиационных работ

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 30 September 2026 at 21:41 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%
22–23.4 / 30.8
partial
Project activity
21.1 / 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
  • The README introduces the project
  • Commits are fresh (9 days)
  • Commits span the whole year (97 commits)
  • A team works on the project (4 authors)

What affected the score

Penalties

Documentation and best practices

  • −3
    license filemissing
  • −3
    review policyno protection
  • −1
    branch protection policyno protection

Project activity

  • −5
    last releaseno releases or version tags
  • −3
    top author's share of commits — 84%
  • −2
    weekly activity — 3 weeks

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
  • Activity
    +5
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Documentation
    +3
    add a license filelicense filewhy: the terms of use are stated, not guessed
  • Documentation
    +3
    set up a review policyreview policywhy: a change is reviewed, and the history stays readable
  • share the work with other contributors+3
  • spread work across more weeks instead of bursts+2
  • set up a branch protection policy+1