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

applicable weight 80%

imbok/cosmos-ontology-sites

Language: Python
branch master

Двуязычные статические сайты с документацией об онтологиях COSMOS и IMT

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 22:39 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 81%
15–19.7 / 25
partial
Project activity
16.2 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.3–18.8 / 18.8
partial
Issues
16.9 / 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: tests directory, Dockerfile, 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
  • Open issues do not pile up (65 days)
  • SourceCraft CI is configured
  • Commits span the whole year (49 commits)
  • Commits are fresh (63 days)
  • CI checks pull requests

What affected the score

Penalties

Documentation and best practices

  • −3
    README3,393 chars, no quickstart
  • −2
    dependency lockfilemissing
  • −<1
    share of short commit messages — 4%

Project activity

  • −4
    last releaseno releases or version tags
  • −2
    unique authors — 2 authors
  • −1
    weekly activity — 3 weeks
  • −1
    top author's share of commits — 61%
  • −<1
    last commit — 63 days

Issues

  • −2
    age of open issues — 65 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
    tests directorydata not collected
  • up to −2
    Dockerfiledata 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
  • Documentation
    +3
    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
  • Documentation
    +2
    add a dependency lockfiledependency lockfilewhy: the build and the checks are reproducible for whoever takes the code
  • bring in a second maintainer+2
  • work through the stale open issues+2
  • spread work across more weeks instead of bursts+1
  • share the work with other contributors+1
  • make a commit soon+<1
  • write meaningful commit messages+<1