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

applicable weight 65%

yndx-bulanna-5kx2pz/puter

Language: TypeScript
branch main
imported from GitHub

🌐 The Internet Computer! Free, Open-Source, and Self-Hostable.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 22:46 UTC — part unavailable

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
26.4 / 30.8
scored
Project activitysignal coverage 33%
9.3–29.8 / 30.8
partial
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
0–15.4 / 15.4
collection failed
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: TODO/FIXME density
couldn't see it
the platform's window was truncated: a deep file or a recent version may have fallen outside it
Not measured: commits in the last year, weekly activity, top author's share of commits, unique authors
data not collected
the surface didn't answer this collection run

Strengths

what's already done
  • The README introduces the project
  • Commits are fresh (59 days)
  • Releases keep coming (63 days)
  • The license file is in place
  • Tests live in the repository

What affected the score

Penalties

Documentation and best practices

  • −3
    review policyno protection
  • −1
    branch protection policyno protection

Project activity

  • −1
    last release — 63 days
  • −<1
    last commit — 59 days

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

Project activity

  • up to −5
    commits in the last yeardata not collected
  • up to −5
    weekly activitydata not collected
  • up to −5
    top author's share of commitsdata not collected
  • up to −5
    unique authorsdata not collected

CI/CD

  • up to −12
    CI runsdata not collected

Code health

  • up to −15
    TODO/FIXME densitydata 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
  • Documentation
    +3
    set up a review policyreview policywhy: a change is reviewed, and the history stays readable
  • Documentation
    +1
    set up a branch protection policybranch protection policywhy: a change is reviewed, and the history stays readable
  • publish a release or tag a version+1
  • make a commit soon+<1