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

applicable weight 65%

zylex/manytask

Language: Python
branch main

The auto solution checking system for YSDA; server, storing grades and managing deadlines

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 21:25 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
19.9 / 30.8
scored
Project activity
23 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
9.2–18.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

Strengths

what's already done
  • SourceCraft CI is configured
  • Commits span the whole year (101 commits)
  • Work goes on without long pauses (17 weeks)
  • Contributions are spread across authors
  • A team works on the project (14 authors)

What affected the score

Penalties

Documentation and best practices

  • −4
    README4,438 chars, no quickstart
  • −3
    dependency lockfilemissing
  • −3
    review policyno protection
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 2%

Project activity

  • −5
    last releaseno releases or version tags
  • −3
    last commit — 207 days

CI/CD

  • −5
    CI configuration contents

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

Code health

  • up to −15
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • Activity
    +5
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • CI/CD
    +5
    run CI on pull requests, not only on pushes to the default branchCI configuration contentswhy: a change is reviewed, and the history stays readableevidence: CI config .sourcecraft/ci.yaml, snapshot of 8 October 2026
  • Documentation
    +4
    add a quickstart section to the READMEREADMEwhy: a newcomer can tell how to run the project and where to lookevidence: file README.md, snapshot of 8 October 2026
  • add a dependency lockfile+3
  • set up a review policy+3
  • make a commit soon+3
  • set up a branch protection policy+1
  • write meaningful commit messages+<1