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

applicable weight 65%

aladin/pandoc-mcp

Language: Rust
branch main
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 29 September 2026 at 22:49 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
23.3 / 30.8
scored
Project activity
20.8 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
13.8–23.1 / 23.1
partial
Issuesthe tracker is empty or not set up
no data
Code health
15.4 / 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
  • Almost no marked debt in the code
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (9 days)
  • Releases keep coming (9 days)

What affected the score

Penalties

Documentation and best practices

  • −3
    license filemissing
  • −3
    review policyno protection
  • −1
    contributing guidemissing
  • −<1
    share of short commit messages — 9%

Project activity

  • −4
    weekly activity — 1 week
  • −3
    top author's share of commits — 82%
  • −3
    unique authors — 2 authors
  • −1
    commits in the last year — 11 commits

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
  • Activity
    +4
    spread work across more weeks instead of burstsweekly activity — 1 weekwhy: the repository shows it is alive, not abandoned
  • Documentation
    +3
    add a license filelicense filewhy: the terms of use are stated, not guessed
  • Documentation
    +3
    set up a review policyreview policywhy: a change is reviewed, and the history stays readable
  • share the work with other contributors+3
  • bring in a second maintainer+3
  • add a contributing guide+1
  • commit more often+1
  • write meaningful commit messages+<1