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

applicable weight 65%

testkek18-5/kometa

Language: Python
branch master

Python script to update metadata information for items in plex as well as automatically build collections and playlists. The Wiki Documentation is linked below.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 19:03 UTC — part unavailable

What the 100 is made of

category weight
Documentation 20Activity 20Security 20CI/CD 15Issues 15Code health 10

The light segments — Security: will appear with a member token; Issues: the tracker is empty or not set up. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practicessignal coverage 86%
19–23.4 / 30.8
partial
Project activity
10.3 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–11.5 / 23.1
partial
Issuesthe tracker is empty or not set up
no data
Code health
0–15.4 / 15.4
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, 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 README introduces the project
  • Contributions are spread across authors
  • A team works on the project (10 authors)
  • The license file is in place
  • Documentation has its own directory

What affected the score

Penalties

Documentation and best practices

  • −3
    dependency lockfilemissing
  • −3
    review policyno protection
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 4%

Project activity

  • −5
    last commit — 556 days
  • −5
    commits in the last year — 0 commits
  • −5
    weekly activity — 0 weeks
  • −5
    last releaseno releases or version tags

CI/CD

  • −12
    SourceCraft CI configurationmissing

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 −3
    tests directorydata not collected
  • up to −1
    contributing guidedata not collected

CI/CD

  • up to −12
    CI runsdata not collected

Code health

  • up to −15
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • CI/CD
    +12
    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
  • Activity
    +5
    make a commit soonlast commit — 556 dayswhy: the repository shows it is alive, not abandoned
  • Activity
    +5
    commit more oftencommits in the last year — 0 commitswhy: the repository shows it is alive, not abandoned
  • spread work across more weeks instead of bursts+5
  • publish a release or tag a version+5
  • add a dependency lockfile+3
  • set up a review policy+3
  • set up a branch protection policy+1
  • write meaningful commit messages+<1