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

applicable weight 80%

krivosheina-daryaa/real-developer-case-simulation

Language: TypeScript
branch main

Simulation of a real developer project with messy PRs, issues, branches, and history. Focus on YAML and JSON configurations.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 21:25 UTC — not all categories measured

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 practices
8.2 / 25
scored
Project activity
4.8 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
5.3 / 18.8
scored
Code health
12.5 / 12.5
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 README introduces the project

What affected the score

Penalties

Documentation and best practices

  • −2
    license filemissing
  • −2
    tests directorymissing
  • −2
    docs directorymissing
  • −2
    Dockerfilemissing
  • −2
    dependency lockfilemissing
  • −2
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 11%

Project activity

  • −3
    top author's share of commits — 100%
  • −3
    unique authors — 1 author
  • −3
    last releaseno releases or version tags
  • −3
    share of unanswered pull requests — 100%sample: 10 of 10
  • −3
    share of closed pull requests — 0%window: 50 PRs, sample threshold: 10 of 10
  • −2
    weekly activity — 1 week
  • −2
    last commit — 207 days
  • −1
    commits in the last year — 9 commits

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −9
    share of unanswered issues — 100%sample: 10 of 10
  • −4
    age of open issues — 207 days13 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
  • 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
  • Issues
    +9
    respond to issuesshare of unanswered issues — 100%why: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • Issues
    +4
    work through the stale open issuesage of open issues — 207 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • share the work with other contributors+3
  • bring in a second maintainer+3
  • publish a release or tag a version+3
  • respond to pull requests+3
  • close pull requests+3
  • add a license file+2
  • write tests for the project+2
  • write project documentation+2
  • containerize the project — add a Dockerfile+2
  • add a dependency lockfile+2
  • set up a review policy+2
  • spread work across more weeks instead of bursts+2
  • make a commit soon+2
  • add a contributing guide+1
  • set up a branch protection policy+1
  • commit more often+1
  • write meaningful commit messages+<1