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

applicable weight 80%

guitariz91/tasker

Language: Kotlin
branch trunk
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 5 October 2026 at 21:21 UTC — part unavailable

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 86%
13.1–16.7 / 25
partial
Project activity
14.7 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
9.8–17.3 / 18.8
partial
Issues
18.7 / 18.8
scored
Code health
0–12.5 / 12.5
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: Dockerfile, contributing guide, 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
  • Issues are closed quickly (today)
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (3 days)
  • Commits span the whole year (340 commits)

What affected the score

Penalties

Documentation and best practices

  • −2
    license filemissing
  • −2
    dependency lockfilemissing
  • −2
    review policyno protection
  • −1
    branch protection policyno protection

Project activity

  • −4
    last releaseno releases or version tags
  • −4
    top author's share of commits — 99%
  • −2
    unique authors — 2 authors

CI/CD

  • −2
    CI configuration contents

Issues

  • −<1
    issue resolution time — today50 of 179 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
    Dockerfiledata not collected
  • up to −1
    contributing guidedata not collected

CI/CD

  • up to −8
    CI runsdata not collected

Code health

  • up to −13
    TODO/FIXME densitydata 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
  • Activity
    +4
    share the work with other contributorstop author's share of commits — 99%why: the work does not rest on a single person
  • Documentation
    +2
    add a license filelicense filewhy: the terms of use are stated, not guessed
  • add a dependency lockfile+2
  • set up a review policy+2
  • bring in a second maintainer+2
  • run CI on pull requests, not only on pushes to the default branch+2
  • set up a branch protection policy+1
  • close issues faster+<1