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

applicable weight 80%

covvex/shareform

Language: JavaScript
branch main

Простой способ делится данными для заполнения форм

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 19:11 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
9.8 / 25
scored
Project activity
16.6 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
0–7.5 / 18.8
partial
Issues
5 / 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 license file is in place
  • Documentation has its own directory

What affected the score

Penalties

Documentation and best practices

  • −3
    README300 chars, no quickstart
  • −2
    tests directorymissing
  • −2
    Dockerfilemissing
  • −2
    dependency lockfilemissing
  • −2
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 36%

Project activity

  • −4
    last releaseno releases or version tags
  • −1
    weekly activity — 3 weeks
  • −1
    top author's share of commits — 67%
  • −1
    unique authors — 3 authors
  • −<1
    last commit — 68 days
  • −<1
    commits in the last year — 18 commits

CI/CD

  • −8
    SourceCraft CI configurationmissing
  • −4
    CI configuration contents

Issues

  • −8
    share of unanswered issues — 100%sample: 6 of 10
  • −5
    age of open issues — 353 days19 issues
  • −1
    issue resolution time — 7 days19 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 −8
    CI runsdata not collected

What will raise the score

by strength of impact
  • CI/CD
    +8
    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
    +8
    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
    +5
    work through the stale open issuesage of open issues — 353 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • publish a release or tag a version+4
  • run CI on pull requests, not only on pushes to the default branch+4
  • add a quickstart section to the README+3
  • write tests for the project+2
  • containerize the project — add a Dockerfile+2
  • add a dependency lockfile+2
  • set up a review policy+2
  • close issues faster+1
  • spread work across more weeks instead of bursts+1
  • add a contributing guide+1
  • set up a branch protection policy+1
  • share the work with other contributors+1
  • bring in a second maintainer+1
  • make a commit soon+<1
  • commit more often+<1
  • write meaningful commit messages+<1