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

applicable weight 80%

cppshizoid/dagflow

Language: C++
branch main
mirror

A self-contained, minimal runtime for parallel task execution in C++20.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 4 October 2026 at 21: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 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 83%
17.8–21.9 / 25
partial
Project activity
14.7 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
14.3 / 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
Not measured: Dockerfile, contributing guide
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
  • Almost no marked debt in the code
  • The README introduces the project
  • Commits are fresh (4 days)
  • The license file is in place
  • Tests live in the repository

What affected the score

Penalties

Documentation and best practices

  • −3
    dependency lockfilemissing
  • −<1
    share of short commit messages — 20%

Project activity

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

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −4
    issue resolution time — 3 days3 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 −3
    Dockerfiledata not collected
  • up to −1
    contributing guidedata not collected

CI/CD

  • up to −9
    CI runsdata not collected

What will raise the score

by strength of impact
  • CI/CD
    +9
    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
  • Issues
    +4
    close issues fasterissue resolution time — 3 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • Activity
    +4
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • add a dependency lockfile+3
  • bring in a second maintainer+2
  • share the work with other contributors+2
  • spread work across more weeks instead of bursts+1
  • commit more often+1
  • write meaningful commit messages+<1