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

applicable weight 80%

gravity-ui/icons

Language: TSX
branch main
mirror
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 18:40 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 67%
16.7–25 / 25
partial
Project activity
19.7 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
0 / 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: tests directory, docs directory, Dockerfile, 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
  • The README introduces the project
  • A team works on the project (4 authors)
  • Commits are fresh (44 days)
  • Work goes on without long pauses (7 weeks)
  • The license file is in place

What affected the score

Penalties

Project activity

  • −3
    last release — 255 days
  • −1
    top author's share of commits — 71%
  • −1
    commits in the last year — 14 commits
  • −<1
    weekly activity — 7 weeks
  • −<1
    last commit — 44 days

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −8
    share of unanswered issues — 100%sample: 6 of 10
  • −8
    age of open issues — 594 days9 issues
  • −4
    issue resolution time — 126 days9 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 −3
    tests directorydata not collected
  • up to −3
    docs directorydata not collected
  • up to −3
    Dockerfiledata not collected

CI/CD

  • up to −9
    CI runsdata not collected

Code health

  • up to −13
    TODO/FIXME densitydata 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
  • Issues
    +8
    respond to issuesshare of unanswered issues — 100%why: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • Issues
    +8
    work through the stale open issuesage of open issues — 594 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • close issues faster+4
  • publish a release or tag a version+3
  • share the work with other contributors+1
  • commit more often+1
  • spread work across more weeks instead of bursts+<1
  • make a commit soon+<1