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

applicable weight 80%

lexxi-0/telegram-bdssa-notifier

Language: Python
branch main
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 22:59 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
17.9 / 25
scored
Project activity
14.4 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.3–18.8 / 18.8
partial
Issues
9.4 / 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
  • Open issues do not pile up (30 days)
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (24 days)

What affected the score

Penalties

Documentation and best practices

  • −2
    Dockerfilemissing
  • −2
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection

Project activity

  • −4
    last releaseno releases or version tags
  • −3
    weekly activity — 1 week
  • −2
    unique authors — 2 authors
  • −1
    commits in the last year — 9 commits
  • −<1
    top author's share of commits — 56%

Issues

  • −9
    share of unanswered issues — 100%sample: 5 of 10
  • −<1
    age of open issues — 30 days7 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
  • Issues
    +9
    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
  • Activity
    +4
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Activity
    +3
    spread work across more weeks instead of burstsweekly activity — 1 weekwhy: the repository shows it is alive, not abandoned
  • containerize the project — add a Dockerfile+2
  • set up a review policy+2
  • bring in a second maintainer+2
  • add a contributing guide+1
  • set up a branch protection policy+1
  • commit more often+1
  • share the work with other contributors+<1
  • work through the stale open issues+<1