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

applicable weight 80%

lct-hackaton-2026/case-01-robotic-solutions-platform-team-21

Language: TypeScript
branch main

ЛЦТ 2026 · Кейс 01 · Команда 21 — Платформа подбора роботизированных решений с расчётом экономического эффекта и визуализацией работы роботов на объекте

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 29 September 2026 at 21:45 UTC — part unavailable

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 practicessignal coverage 95%
17.9–19 / 25
partial
Project activity
19.5 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.3–18.8 / 18.8
partial
Issues
17.3 / 18.8
scored
Code health
0–12.5 / 12.5
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
  • Open issues do not pile up (22 days)
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (9 days)
  • Commits span the whole year (402 commits)

What affected the score

Penalties

Documentation and best practices

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

Project activity

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

Issues

  • −1
    issue resolution time — 3 days50 of 91 issues

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

Code health

  • up to −13
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • 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
  • Documentation
    +2
    set up a review policyreview policywhy: a change is reviewed, and the history stays readable
  • close issues faster+1
  • spread work across more weeks instead of bursts+1
  • set up a branch protection policy+1