# qipparu/testk

- Platform link: https://sourcecraft.dev/qipparu/testk
- Snapshot date: 2026-10-08
- Generated at: 2026-10-09 10:29 UTC

## Score

**17–46** (F–D — starting point–room to grow), applicable weight 80%.

## Categories

| Category | Weight (nominal / applied) | State | Score | Coverage |
| --- | --- | --- | --- | --- |
| Documentation and best practices | 20 / 25 | partial | 35.33–63.9 | 71% |
| CI/CD | 15 / 18.75 | partial | 0–50 | 50% |
| Security | 20 / 0 | no data | – | 0% |
| Project activity | 20 / 25 | scored | 22.45 | 100% |
| Issues | 15 / 18.75 | scored | 11.8 | 100% |
| Code health | 10 / 12.5 | collection failed | 0–100 | 0% |

## Strengths

- **unique authors** (Project activity): earned 4.17 of 4.17
- **license file** (Documentation and best practices): earned 2.38 of 2.38
- **contributing guide** (Documentation and best practices): earned 1.19 of 1.19

## Recommendations

- **work through the stale open issues** [critical] (Issues) — age of open issues, may return up to +16.54 (an outside contributor gets an answer, and their work is not lost)
- **add a SourceCraft CI configuration (.sourcecraft/ci.yaml); the service does not see external CI** [critical] (CI/CD) — SourceCraft CI configuration, may return up to +9.38 (the build and the checks are reproducible for whoever takes the code)
- **make a commit soon** [medium] (Project activity) — last commit, may return up to +4.17 (the repository shows it is alive, not abandoned)
- **commit more often** [medium] (Project activity) — commits in the last year, may return up to +4.17 (the repository shows it is alive, not abandoned)
- **spread work across more weeks instead of bursts** [medium] (Project activity) — weekly activity, may return up to +4.17 (the repository shows it is alive, not abandoned)
- **publish a release or tag a version** [medium] (Project activity) — last release, may return up to +4.17 (the build and the checks are reproducible for whoever takes the code)
- **add a quickstart section to the README** [medium] (Documentation and best practices) — README, may return up to +2.86 (a newcomer can tell how to run the project and where to look)
- **share the work with other contributors** [medium] (Project activity) — top author's share of commits, may return up to +2.72 (the work does not rest on a single person)
- **add a dependency lockfile** [medium] (Documentation and best practices) — dependency lockfile, may return up to +2.38 (the build and the checks are reproducible for whoever takes the code)
- **set up a review policy** [medium] (Documentation and best practices) — review policy, may return up to +2.38 (a change is reviewed, and the history stays readable)
- **set up a branch protection policy** [optional] (Documentation and best practices) — branch protection policy, may return up to +1.19 (a change is reviewed, and the history stays readable)
- **write meaningful commit messages** [optional] (Documentation and best practices) — share of short commit messages, may return up to +0.21 (a change is reviewed, and the history stays readable)

## 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** — partial
  - tests directory: up to −2.38 — the platform returned incomplete data — the value could not be determined
  - docs directory: up to −2.38 — the platform returned incomplete data — the value could not be determined
  - Dockerfile: up to −2.38 — the platform returned incomplete data — the value could not be determined
- **CI/CD** — partial
  - CI runs: up to −9.38 — access to the source is closed
- **Code health** — collection failed
  - TODO/FIXME density: up to −12.5 — the platform returned incomplete data — the value could not be determined

## Not counted in the score, and why

- **Security** — no data
  - the basis was not saved: there was nothing to measure, or the reason was not recorded in the snapshot