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

applicable weight 80%

volkovpartilaholin/gamekeys-frontend

Language: TypeScript
branch main

GameKeys — сравнение цен на игры (Playerok, Kupikod, Бука, Zaka-zaka, Plati Market) + отслеживание цен

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 2 October 2026 at 21:41 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 practicessignal coverage 76%
15.2–21.1 / 25
partial
Project activity
17.1 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
9.8–17.3 / 18.8
partial
Issues
18.1 / 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
Not measured: tests directory, Dockerfile, contributing guide
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 (16 days)
  • Almost no marked debt in the code
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (6 days)

What affected the score

Penalties

Documentation and best practices

  • −2
    license filemissing
  • −1
    review policybasic protection
  • −<1
    branch protection policybasic protection
  • −<1
    share of short commit messages — 5%

Project activity

  • −4
    last releaseno releases or version tags
  • −2
    weekly activity — 2 weeks
  • −1
    unique authors — 3 authors
  • −1
    top author's share of commits — 60%
  • −<1
    commits in the last year — 20 commits

CI/CD

  • −2
    CI configuration contents

Issues

  • −1
    issue resolution time — 1 day12 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 −8
    CI runsdata not collected

What will raise the score

by strength of impact
  • Activity
    +4
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Documentation
    +2
    add a license filelicense filewhy: the terms of use are stated, not guessed
  • Activity
    +2
    spread work across more weeks instead of burstsweekly activity — 2 weekswhy: the repository shows it is alive, not abandoned
  • run CI on pull requests, not only on pushes to the default branch+2
  • set up a review policy+1
  • bring in a second maintainer+1
  • share the work with other contributors+1
  • close issues faster+1
  • set up a branch protection policy+<1
  • commit more often+<1
  • write meaningful commit messages+<1