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

applicable weight 80%

ayab/ayab-fbs

Language: Python
branch ayab-fork
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 22:31 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%
10.4–14 / 25
partial
Project activity
5.9 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
15.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: docs directory, 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
  • The license file is in place
  • Tests live in the repository
  • The build is described by a Dockerfile
  • Commit messages are meaningful

What affected the score

Penalties

Documentation and best practices

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

Project activity

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

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −3
    age of open issues — 89 days4 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
    docs directorydata not collected
  • up to −1
    contributing guidedata not collected

CI/CD

  • up to −9
    CI runsdata not collected

Code health

  • up to −13
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • CI/CD
    +9
    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
  • Documentation
    +5
    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
  • Activity
    +4
    share the work with other contributorstop author's share of commits — 100%why: the work does not rest on a single person
  • bring in a second maintainer+4
  • publish a release or tag a version+4
  • work through the stale open issues+3
  • spread work across more weeks instead of bursts+3
  • commit more often+3
  • add a dependency lockfile+2
  • set up a review policy+2
  • set up a branch protection policy+1
  • make a commit soon+1
  • write meaningful commit messages+<1