Some interest. A stronger README and CI would help.
Stochastic, slippery hill climber with backtracking for attacking classical ciphers.
Documentation
58
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under MIT.
Engineering
29
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
No dependency lockfile found (−70 pts).
→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Test files detected (ciphers/tests).
Project health
68
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 5Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 13Watchers
Responsiveness
- —Median issue response
- <1hMedian PR merge time
- 1Open issues
Repository files74 root entries
- ciphersGood: Test files detected (ciphers/tests).
- tests
- tools
- .gitignoreGood: .gitignore present.
- amsco_solver.c
- amsco_solver.h
- autokey.c
- beaufort.c
- bifid_solver.c
- bifid_solver.h
- bifid.c
- cadenus_solver.c
- cadenus_solver.h
- cipher.txt
- CLAUDE.md
- colossus.c
- colossus.h
- columnar_solver.c
- columnar_solver.h
- crib.txt
- dict.c
- engine.c
- engine.h
- english_quadgrams.txt
- example.sh
- grille_solver.c
- grille_solver.h
- hill_solver.c
- hill_solver.h
- hill.c
- homophonic_solver.c
- homophonic_solver.h
- indep_solver.c
- indep_solver.h
- LICENSEGood: Licensed under MIT.
- makefile
- myszkowski_solver.c
- myszkowski_solver.h
- nihilist_solver.c
- nihilist_solver.h
- optimal_cycleword.c
- OxfordEnglishWords.txt
- parse.c
- perioc.c
- permutation_solver.c
- permutation_solver.h
- playfair_solver.c
- playfair_solver.h
- playfair.c
- polyalpha_solver.c
- polyalpha_solver.h
- porta.c
- quagmire.c
- railfence_solver.c
- railfence_solver.h
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.Good: README has code examples.Good: README links to a live demo or deployed app.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Good: README documents how to run the project.
- redefence_solver.c
- redefence_solver.h
- route_solver.c
- route_solver.h
- scoring.c
- scoring.h
- swagman_solver.c
- swagman_solver.h
- trans_common.c
- trans_common.h
- transmatrix_solver.c
- transmatrix_solver.h
- transpositions.c
- trifid_solver.c
- trifid_solver.h
- trifid.c
- utils.c
- vigenere.c