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

applicable weight 65%

ivi-ippolitov/enummethods

Language: Go
branch main

This tool is used to automatically complement the data types used to describe enumerations with standard methods that satisfy the interface Enumerator and json.Marshaler, json.Unmarshaler

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 19:16 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
15.9 / 30.8
scored
Project activity
4 / 30.8
scored
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
11.6 / 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
  • The README introduces the project
  • Tests live in the repository
  • Dependency versions are pinned

What affected the score

Penalties

Documentation and best practices

  • −3
    license filemissing
  • −3
    docs directorymissing
  • −3
    Dockerfilemissing
  • −3
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 13%

Project activity

  • −5
    top author's share of commits — 100%
  • −5
    unique authors — 1 author
  • −5
    last commit — 324 days
  • −5
    last release — 324 days
  • −4
    commits in the last year — 1 commit
  • −4
    weekly activity — 1 week

CI/CD

  • −12
    SourceCraft CI configurationmissing

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 −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
    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
  • make a commit soon+5
  • publish a release or tag a version+5
  • commit more often+4
  • work through the TODO/FIXME marks in the code+4
  • spread work across more weeks instead of bursts+4
  • add a license file+3
  • write project documentation+3
  • containerize the project — add a Dockerfile+3
  • set up a review policy+3
  • add a contributing guide+1
  • set up a branch protection policy+1
  • write meaningful commit messages+<1