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

applicable weight 65%

madhoney/gherkin-javascript

Language: TypeScript
branch main
imported from GitHub

[READ-ONLY] Gherkin for JavaScript - subtree of monorepo https://github.com/cucumber/cucumber -- moved to https://github.com/cucumber/gherkin

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 19:35 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
17.6 / 30.8
scored
Project activitysignal coverage 83%
7.3–12.4 / 30.8
partial
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
13.9 / 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
Not measured: last release
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
  • A team works on the project (9 authors)
  • The license file is in place
  • Tests live in the repository

What affected the score

Penalties

Documentation and best practices

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

Project activity

  • −5
    last commit — 1,431 days
  • −5
    commits in the last year — 0 commits
  • −5
    weekly activity — 0 weeks
  • −3
    top author's share of commits — 84%

CI/CD

  • −12
    SourceCraft CI configurationmissing

Code health

  • −1
    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

Project activity

  • up to −5
    last releasedata not collected

CI/CD

  • up to −12
    CI runsdata 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 — 1,431 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
  • share the work with other contributors+3
  • write project documentation+3
  • containerize the project — add a Dockerfile+3
  • add a dependency lockfile+3
  • set up a review policy+3
  • work through the TODO/FIXME marks in the code+1
  • set up a branch protection policy+1