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

applicable weight 70%

dimanovak2010/case-project-one

branch main

A 3-in-a-row game project with various themed events.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 70%analysed 17 September 2026 at 18:46 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
6 / 28.6
scored
Project activity
13.4 / 28.6
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.1–19.7 / 21.4
partial
Issues
14.6 / 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
    README273 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 — 17%

Project activity

  • −5
    last releaseno releases or version tags
  • −3
    weekly activity — 1 week
  • −2
    unique authors — 2 authors
  • −2
    last commit — 152 days
  • −2
    commits in the last year — 6 commits
  • −1
    top author's share of commits — 67%

CI/CD

  • −2
    CI configuration contents

Issues

  • −7
    age of open issues — 153 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

CI/CD

  • up to −9
    CI runsdata not collected

What will raise the score

by strength of impact
  • Issues
    +7
    work through the stale open issuesage of open issues — 153 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
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Activity
    +3
    spread work across more weeks instead of burstsweekly activity — 1 weekwhy: the repository shows it is alive, not abandoned
  • 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
  • bring in a second maintainer+2
  • run CI on pull requests, not only on pushes to the default branch+2
  • make a commit soon+2
  • commit more often+2
  • add a contributing guide+1
  • set up a branch protection policy+1
  • share the work with other contributors+1
  • write meaningful commit messages+<1