# yndx-a-koptsov/palindrome

- Platform link: https://sourcecraft.dev/yndx-a-koptsov/palindrome
- Modifiers: mirror (missing branch and review policies are not penalised: they cannot be set here)
- Snapshot date: 2026-10-08
- Generated at: 2026-10-09 10:09 UTC

## Score

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

## Categories

| Category | Weight (nominal / applied) | State | Score | Coverage |
| --- | --- | --- | --- | --- |
| Documentation and best practices | 20 / 25 | scored | 46.85 | 100% |
| CI/CD | 15 / 18.75 | partial | 0–50 | 50% |
| Security | 20 / 0 | no data | – | 0% |
| Project activity | 20 / 25 | scored | 20.42 | 100% |
| Issues | 15 / 18.75 | scored | 9.12 | 100% |
| Code health | 10 / 12.5 | scored | 100 | 100% |

## Strengths

- **TODO/FIXME density** (Code health): earned 12.5 of 12.5
- **license file** (Documentation and best practices): earned 2.78 of 2.78
- **dependency lockfile** (Documentation and best practices): earned 2.78 of 2.78

## Recommendations

- **work through the stale open issues** [critical] (Issues) — age of open issues, may return up to +17.04 (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)
- **share the work with other contributors** [medium] (Project activity) — top author's share of commits, may return up to +4.17 (the work does not rest on a single person)
- **bring in a second maintainer** [medium] (Project activity) — unique authors, may return up to +4.17 (the work does not rest on a single person)
- **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)
- **make a commit soon** [medium] (Project activity) — last commit, may return up to +4.06 (the repository shows it is alive, not abandoned)
- **add a quickstart section to the README** [medium] (Documentation and best practices) — README, may return up to +3.33 (a newcomer can tell how to run the project and where to look)
- **write tests for the project** [medium] (Documentation and best practices) — tests directory, may return up to +2.78 (the build and the checks are reproducible for whoever takes the code)
- **write project documentation** [medium] (Documentation and best practices) — docs directory, may return up to +2.78 (a newcomer can tell how to run the project and where to look)
- **containerize the project — add a Dockerfile** [medium] (Documentation and best practices) — Dockerfile, may return up to +2.78 (a newcomer can tell how to run the project and where to look)
- **spread work across more weeks instead of bursts** [optional] (Project activity) — weekly activity, may return up to +1.88 (the repository shows it is alive, not abandoned)
- **commit more often** [optional] (Project activity) — commits in the last year, may return up to +1.46 (the repository shows it is alive, not abandoned)
- **add a contributing guide** [optional] (Documentation and best practices) — contributing guide, may return up to +1.39 (an outside contributor gets an answer, and their work is not lost)
- **write meaningful commit messages** [optional] (Documentation and best practices) — share of short commit messages, may return up to +0.23 (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.

- **CI/CD** — partial
  - CI runs: up to −9.38 — access to the source is closed

## 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