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

applicable weight 65%

arhone/ablock

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 19:08 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 practices
0–30.8 / 30.8
collection failed
Project activity
0 / 30.8
scored
Securitywill appear with a member token
no data
CI/CD
0–23.1 / 23.1
collection failed
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: README, license file, tests directory, docs directory, Dockerfile, dependency lockfile, contributing guide, branch protection policy, review policy, SourceCraft CI configuration, CI configuration contents, TODO/FIXME density
data not collected
the surface didn't answer this collection run

Strengths

what's already done

No metric has a full score yet

What affected the score

Penalties

Project activity

  • −10
    commits in the last year — 0 commits
  • −10
    weekly activity — 0 weeks
  • −10
    last releaseno releases or version tags

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 −9
    READMEdata not collected
  • up to −3
    license filedata not collected
  • up to −3
    tests directorydata not collected
  • up to −3
    docs directorydata not collected
  • up to −3
    Dockerfiledata not collected
  • up to −3
    dependency lockfiledata not collected
  • up to −3
    review policydata not collected
  • up to −2
    contributing guidedata not collected
  • up to −2
    branch protection policydata not collected

CI/CD

  • up to −9
    SourceCraft CI configurationdata not collected
  • up to −9
    CI runsdata not collected
  • up to −5
    CI configuration contentsdata not collected

Code health

  • up to −15
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • Activity
    +10
    commit more oftencommits in the last year — 0 commitswhy: the repository shows it is alive, not abandoned
  • Activity
    +10
    spread work across more weeks instead of burstsweekly activity — 0 weekswhy: the repository shows it is alive, not abandoned
  • Activity
    +10
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code