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

applicable weight 80%

elfenmail/pet-ontology

Language: TypeScript
branch main
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 8 October 2026 at 21:57 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
7.1 / 25
scored
Project activity
14.2 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.3–18.8 / 18.8
partial
Issues
18.1 / 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
  • Open issues do not pile up (today)
  • Almost no marked debt in the code
  • SourceCraft CI is configured
  • Issues are closed quickly (today)
  • Commits are fresh (today)

What affected the score

Penalties

Documentation and best practices

  • −7
    READMEmissing
  • −2
    license filemissing
  • −2
    docs directorymissing
  • −2
    Dockerfilemissing
  • −2
    review policyno protection
  • −1
    contributing guidemissing

Project activity

  • −4
    last releaseno releases or version tags
  • −2
    unique authors — 2 authors
  • −2
    weekly activity — 2 weeks
  • −1
    top author's share of commits — 71%
  • −1
    commits in the last year — 7 commits

Issues

  • −1
    issue resolution time — today6 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
  • Documentation
    +7
    add a quickstart section to the READMEREADMEwhy: a newcomer can tell how to run the project and where to look
  • Activity
    +4
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Documentation
    +2
    add a license filelicense filewhy: the terms of use are stated, not guessed
  • write project documentation+2
  • containerize the project — add a Dockerfile+2
  • set up a review policy+2
  • bring in a second maintainer+2
  • spread work across more weeks instead of bursts+2
  • share the work with other contributors+1
  • commit more often+1
  • add a contributing guide+1
  • close issues faster+1