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

applicable weight 65%

mezentsevs/typing-trainer-landing

Language: Vue
branch main

🌐 A landing page for 'Typing trainer' - static website presenting the typing trainer application. Built with TypeScript, Nuxt, Vue, and Tailwindcss. Contains the source code and build configuration for the project's landing page.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 18:49 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
16.1 / 30.8
scored
Project activity
16.6 / 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 README introduces the project
  • Commits span the whole year (47 commits)
  • Work goes on without long pauses (6 weeks)
  • The license file is in place

What affected the score

Penalties

Documentation and best practices

  • −3
    tests directorymissing
  • −3
    docs directorymissing
  • −3
    Dockerfilemissing
  • −3
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 4%

Project activity

  • −5
    last releaseno releases or version tags
  • −4
    top author's share of commits — 96%
  • −3
    unique authors — 2 authors
  • −2
    last commit — 134 days
  • −1
    weekly activity — 6 weeks

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
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Activity
    +4
    share the work with other contributorstop author's share of commits — 96%why: the work does not rest on a single person
  • write tests for the project+3
  • write project documentation+3
  • containerize the project — add a Dockerfile+3
  • set up a review policy+3
  • bring in a second maintainer+3
  • make a commit soon+2
  • add a contributing guide+1
  • set up a branch protection policy+1
  • spread work across more weeks instead of bursts+1
  • write meaningful commit messages+<1