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

applicable weight 70%

3y3-1/test-repository-with-long-name

branch master

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 70%analysed 17 September 2026 at 18:53 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; Code health. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practices
4.9 / 28.6
scored
Project activity
0 / 28.6
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.1–19.7 / 21.4
partial
Issues
0 / 21.4
scored
Code health
no data
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

Strengths

what's already done
  • SourceCraft CI is configured

What affected the score

Penalties

Documentation and best practices

  • −3
    README1,240 chars, no quickstart
  • −3
    license filemissing
  • −3
    tests directorymissing
  • −3
    docs directorymissing
  • −3
    Dockerfilemissing
  • −3
    dependency lockfilemissing
  • −3
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection
  • −1
    share of short commit messages — 100%

Project activity

  • −5
    last commit — 594 days
  • −5
    commits in the last year — 0 commits
  • −5
    weekly activity — 0 weeks
  • −5
    top author's share of commits — 100%
  • −5
    unique authors — 1 author
  • −5
    last releaseno releases or version tags

CI/CD

  • −2
    CI configuration contents

Issues

  • −21
    age of open issues — 573 days1 issue

Not measured — interval width

Not a penalty: the lower bound of the score counts the metric as zero, the upper bound as full

CI/CD

  • up to −9
    CI runsdata not collected

What will raise the score

by strength of impact
  • Issues
    +21
    work through the stale open issuesage of open issues — 573 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • Activity
    +5
    make a commit soonlast commit — 594 dayswhy: the repository shows it is alive, not abandoned
  • Activity
    +5
    commit more oftencommits in the last year — 0 commitswhy: the repository shows it is alive, not abandoned
  • spread work across more weeks instead of bursts+5
  • share the work with other contributors+5
  • bring in a second maintainer+5
  • publish a release or tag a version+5
  • add a quickstart section to the README+3
  • add a license file+3
  • write tests for the project+3
  • write project documentation+3
  • containerize the project — add a Dockerfile+3
  • add a dependency lockfile+3
  • set up a review policy+3
  • run CI on pull requests, not only on pushes to the default branch+2
  • add a contributing guide+1
  • set up a branch protection policy+1
  • write meaningful commit messages+1