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

applicable weight 80%

vitalygashkov-org/rucens

Language: Batchfile
branch main
imported from GitHub

Registry of IP ranges and domains operating with restrictions in Russia

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%
7.6–15.9 / 25
partial
Project activity
15.4 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
7.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: tests directory, docs directory, Dockerfile, 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
  • Commits span the whole year (38 commits)
  • Work goes on without long pauses (10 weeks)
  • Dependency versions are pinned

What affected the score

Penalties

Documentation and best practices

  • −3
    README372 chars, no quickstart
  • −2
    license filemissing
  • −2
    review policyno protection
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 24%

Project activity

  • −4
    last releaseno releases or version tags
  • −3
    top author's share of commits — 87%
  • −2
    unique authors — 2 authors
  • −1
    last commit — 86 days

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −9
    age of open issues — 409 days4 issues
  • −2
    issue resolution time — 7 days4 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 −2
    tests directorydata not collected
  • up to −2
    docs directorydata not collected
  • up to −2
    Dockerfiledata not collected
  • up to −1
    contributing guidedata 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
    +9
    work through the stale open issuesage of open issues — 409 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • Activity
    +4
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • add a quickstart section to the README+3
  • share the work with other contributors+3
  • add a license file+2
  • set up a review policy+2
  • close issues faster+2
  • bring in a second maintainer+2
  • set up a branch protection policy+1
  • make a commit soon+1
  • write meaningful commit messages+<1