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

applicable weight 80%

volkovpartilaholin/poe2-kit

Language: TypeScript
branch main

PoE2 Kit — free companion overlay for Path of Exile 2: price check, boss timer, SSF craft plans, PoB2 combo import. Full Russian-client support. No game memory access, no automation. Free forever — optional support (SBP / WebMoney) in README.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 8 October 2026 at 21:46 UTC — part unavailable

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 90%
19–21.4 / 25
partial
Project activity
18 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
9.8–17.3 / 18.8
partial
Issues
18.8 / 18.8
scored
Code health
0–12.5 / 12.5
collection failed
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, TODO/FIXME density
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
  • Open issues do not pile up (13 days)
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (today)
  • Commits span the whole year (331 commits)

What affected the score

Penalties

Documentation and best practices

  • −2
    review policyno protection
  • −1
    branch protection policyno protection

Project activity

  • −4
    top author's share of commits — 100%
  • −2
    unique authors — 2 authors
  • −1
    weekly activity — 4 weeks

CI/CD

  • −2
    CI configuration contents

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 −2
    Dockerfiledata not collected

CI/CD

  • up to −8
    CI runsdata not collected

Code health

  • up to −13
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • Activity
    +4
    share the work with other contributorstop author's share of commits — 100%why: the work does not rest on a single person
  • Documentation
    +2
    set up a review policyreview policywhy: a change is reviewed, and the history stays readable
  • Activity
    +2
    bring in a second maintainerunique authors — 2 authorswhy: the work does not rest on a single person
  • run CI on pull requests, not only on pushes to the default branch+2
  • set up a branch protection policy+1
  • spread work across more weeks instead of bursts+1