# sadsorceror/my-test

- Platform link: https://sourcecraft.dev/sadsorceror/my-test
- Snapshot date: 2026-10-08
- Generated at: 2026-10-09 09:48 UTC

## Score

**38–62** (F–C — starting point–not bad), applicable weight 65%.

## Categories

| Category | Weight (nominal / applied) | State | Score | Coverage |
| --- | --- | --- | --- | --- |
| Documentation and best practices | 20 / 30.77 | scored | 26.19 | 100% |
| CI/CD | 15 / 23.08 | partial | 60–100 | 60% |
| Security | 20 / 0 | no data | – | 0% |
| Project activity | 20 / 30.77 | scored | 50.76 | 100% |
| Issues | 15 / 0 | no data | – | 0% |
| Code health | 10 / 15.38 | collection failed | 0–100 | 0% |

## Strengths

- **SourceCraft CI configuration** (CI/CD): earned 9.23 of 9.23
- **CI configuration contents** (CI/CD): earned 4.62 of 4.62
- **tests directory** (Documentation and best practices): earned 2.93 of 2.93
- **dependency lockfile** (Documentation and best practices): earned 2.93 of 2.93
- **branch protection policy** (Documentation and best practices): earned 1.47 of 1.47

## Recommendations

- **add a quickstart section to the README** [critical] (Documentation and best practices) — README, may return up to +8.79 (a newcomer can tell how to run the project and where to look)
- **publish a release or tag a version** [critical] (Project activity) — last release, may return up to +5.13 (the build and the checks are reproducible for whoever takes the code)
- **spread work across more weeks instead of bursts** [medium] (Project activity) — weekly activity, may return up to +3.59 (the repository shows it is alive, not abandoned)
- **add a license file** [medium] (Documentation and best practices) — license file, may return up to +2.93 (the terms of use are stated, not guessed)
- **write project documentation** [medium] (Documentation and best practices) — docs directory, may return up to +2.93 (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.93 (a newcomer can tell how to run the project and where to look)
- **set up a review policy** [medium] (Documentation and best practices) — review policy, may return up to +2.93 (a change is reviewed, and the history stays readable)
- **bring in a second maintainer** [medium] (Project activity) — unique authors, may return up to +2.56 (the work does not rest on a single person)
- **share the work with other contributors** [medium] (Project activity) — top author's share of commits, may return up to +2.05 (the work does not rest on a single person)
- **add a contributing guide** [optional] (Documentation and best practices) — contributing guide, may return up to +1.47 (an outside contributor gets an answer, and their work is not lost)
- **commit more often** [optional] (Project activity) — commits in the last year, may return up to +1.28 (the repository shows it is alive, not abandoned)
- **write meaningful commit messages** [optional] (Documentation and best practices) — share of short commit messages, may return up to +0.73 (a change is reviewed, and the history stays readable)
- **make a commit soon** [optional] (Project activity) — last commit, may return up to +0.54 (the repository shows it is alive, not abandoned)

## 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.23 — access to the source is closed
- **Code health** — collection failed
  - TODO/FIXME density: up to −15.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
- **Issues** — no data
  - the basis was not saved: there was nothing to measure, or the reason was not recorded in the snapshot