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

applicable weight 70%

andrew-ptichka/ancap-docs

branch main
imported from GitHub

Docs, roadmap & integration guides for ANCAP — create, buy and sell paid AI workflows with ACP. Trust surface for the AI-native capital platform.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 70%analysed 17 September 2026 at 23:01 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; Code health. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practices
13.1 / 28.6
scored
Project activity
10.5 / 28.6
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–10.7 / 21.4
partial
Issues
17.2 / 21.4
scored
Code health
no data
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
  • Issues are closed quickly (today)
  • Commits are fresh (28 days)
  • The license file is in place
  • Documentation has its own directory
  • A contributor guide is in place

What affected the score

Penalties

Documentation and best practices

  • −3
    README1,349 chars, no quickstart
  • −3
    tests directorymissing
  • −3
    Dockerfilemissing
  • −3
    dependency lockfilemissing
  • −3
    review policyno protection
  • −1
    branch protection policyno protection

Project activity

  • −5
    top author's share of commits — 100%
  • −5
    unique authors — 1 author
  • −5
    last releaseno releases or version tags
  • −2
    weekly activity — 2 weeks
  • −2
    commits in the last year — 6 commits

CI/CD

  • −11
    SourceCraft CI configurationmissing

Issues

  • −4
    age of open issues — 132 days4 issues
  • −<1
    issue resolution time — today4 issues

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

What will raise the score

by strength of impact
  • CI/CD
    +11
    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
    share the work with other contributorstop author's share of commits — 100%why: the work does not rest on a single person
  • Activity
    +5
    bring in a second maintainerunique authors — 1 authorwhy: the work does not rest on a single person
  • publish a release or tag a version+5
  • work through the stale open issues+4
  • add a quickstart section to the README+3
  • write tests for the project+3
  • containerize the project — add a Dockerfile+3
  • add a dependency lockfile+3
  • set up a review policy+3
  • spread work across more weeks instead of bursts+2
  • commit more often+2
  • set up a branch protection policy+1
  • close issues faster+<1