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

applicable weight 80%

mem-2026/astro-blog

Language: TypeScript
branch main
imported from GitHub

for edgeone pages

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 22:53 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 76%
15.5–21.4 / 25
partial
Project activity
18.5 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
18.5 / 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, 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
  • Open issues do not pile up (35 days)
  • The README introduces the project
  • Commits span the whole year (111 commits)
  • Work goes on without long pauses (18 weeks)
  • A team works on the project (8 authors)

What affected the score

Penalties

Documentation and best practices

  • −2
    review policyno protection
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 2%

Project activity

  • −4
    last releaseno releases or version tags
  • −2
    top author's share of commits — 83%
  • −<1
    last commit — 35 days

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −<1
    age of open issues — 35 days2 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
    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
  • Activity
    +4
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Documentation
    +2
    set up a review policyreview policywhy: a change is reviewed, and the history stays readable
  • share the work with other contributors+2
  • set up a branch protection policy+1
  • work through the stale open issues+<1
  • make a commit soon+<1
  • write meaningful commit messages+<1