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

applicable weight 65%

valentin-igr/libmdbx

Language: C
branch master

★ Быстрый транзакционный движок хранения ключ-значение ★ Превосходит легендарную LMDB по надежности, возможностям и производительности ★ Используется в сотнях открытых проектах, в том числе в Ethereum.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 23:03 UTC — not all categories measured

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 practices
13.2 / 30.8
scored
Project activity
27.5 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
12–21.2 / 23.1
partial
Issuesthe tracker is empty or not set up
no data
Code health
11.2 / 15.4
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
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (24 days)
  • Commits span the whole year (129 commits)
  • Work goes on without long pauses (36 weeks)

What affected the score

Penalties

Documentation and best practices

  • −3
    tests directorymissing
  • −3
    docs directorymissing
  • −3
    Dockerfilemissing
  • −3
    dependency lockfilemissing
  • −3
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection

Project activity

  • −3
    top author's share of commits — 83%
  • −<1
    last release — 60 days

CI/CD

  • −2
    CI configuration contents

Code health

  • −4
    TODO/FIXME density

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 −9
    CI runsdata not collected

What will raise the score

by strength of impact
  • Code health
    +4
    work through the TODO/FIXME marks in the codeTODO/FIXME densitywhy: the code stays workable: marked debt does not pile up
  • Documentation
    +3
    write tests for the projecttests directorywhy: the build and the checks are reproducible for whoever takes the code
  • Documentation
    +3
    write project documentationdocs directorywhy: a newcomer can tell how to run the project and where to look
  • containerize the project — add a Dockerfile+3
  • add a dependency lockfile+3
  • set up a review policy+3
  • share the work with other contributors+3
  • run CI on pull requests, not only on pushes to the default branch+2
  • add a contributing guide+1
  • set up a branch protection policy+1
  • publish a release or tag a version+<1