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

applicable weight 65%

admsasha/ds2048

Language: C++
branch master

2048 is a mathematics-based puzzle game where you have to slide tiles on a grid to combine them and create a tile with the number 2048. You have to merge the similar number tiles by moving the arrow keys in four different directions. When two tiles with the same number touch, they will merge into one.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 22 September 2026 at 22:00 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; Issues: the tracker is empty or not set up. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practices
9.3 / 30.8
scored
Project activity
5.9 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–11.5 / 23.1
partial
Issuesthe tracker is empty or not set up
no data
Code health
15.4 / 15.4
scored
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
  • Almost no marked debt in the code
  • The license file is in place

What affected the score

Penalties

Documentation and best practices

  • −4
    README517 chars, no quickstart
  • −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 — 25%

Project activity

  • −5
    last commit — 2,605 days
  • −5
    commits in the last year — 0 commits
  • −5
    weekly activity — 0 weeks
  • −5
    last release — 2,605 days
  • −3
    top author's share of commits — 88%
  • −1
    unique authors — 3 authors

CI/CD

  • −12
    SourceCraft CI configurationmissing

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 −12
    CI runsdata not collected

What will raise the score

by strength of impact
  • CI/CD
    +12
    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
    +5
    make a commit soonlast commit — 2,605 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
  • publish a release or tag a version+5
  • add a quickstart section to the README+4
  • share the work with other contributors+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
  • add a contributing guide+1
  • set up a branch protection policy+1
  • bring in a second maintainer+1
  • write meaningful commit messages+<1