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

applicable weight 65%

derbush/all-together-ui

Language: TSX
branch main

ui для all‑together

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 6 October 2026 at 21:44 UTC — not all categories measured

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 86%
23.4–27.8 / 30.8
partial
Project activity
27 / 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
15.4 / 15.4
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
Not measured: Dockerfile, contributing guide
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
  • Almost no marked debt in the code
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (2 days)
  • Commits span the whole year (249 commits)

What affected the score

Penalties

Documentation and best practices

  • −3
    review policyno protection

Project activity

  • −2
    weekly activity — 2 weeks
  • −1
    unique authors — 3 authors
  • −<1
    top author's share of commits — 55%

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 −3
    Dockerfiledata not collected
  • up to −1
    contributing guidedata not collected

CI/CD

  • up to −9
    CI runsdata not collected

What will raise the score

by strength of impact
  • Documentation
    +3
    set up a review policyreview policywhy: a change is reviewed, and the history stays readable
  • Activity
    +2
    spread work across more weeks instead of burstsweekly activity — 2 weekswhy: the repository shows it is alive, not abandoned
  • Activity
    +1
    bring in a second maintainerunique authors — 3 authorswhy: the work does not rest on a single person
  • share the work with other contributors+<1