Huge star count, but README, tests, and CI need real investment.
Collection of various algorithms in mathematics, machine learning, computer science and physics implemented in C++ for educational purposes.
Documentation
64
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Contributing guide is detailed and thorough.
Licensed under MIT.
Engineering
29
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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.
CI is configured (.github/workflows/approved-label.yml).
Issue or PR templates present.
Project health
53
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.
Last pushed 6-12 months ago (−60 pts).
→ A recent commit signals the project is still maintained.
Repository has a description.
.gitignore present.
Repository files41 root entries
- .githubGood: CI is configured (.github/workflows/approved-label.yml).Good: Issue or PR templates present.
- .vscode
- backtracking
- bit_manipulation
- ciphers
- cpu_scheduling_algorithms
- data_structures
- divide_and_conquer
- doc
- dynamic_programming
- games
- geometry
- graph
- graphics
- greedy_algorithms
- hashing
- machine_learning
- math
- numerical_methods
- operations_on_datastructures
- others
- physics
- probability
- range_queries
- scripts
- search
- sorting
- strings
- .clang-format
- .clang-tidy
- .gitignoreGood: .gitignore present.
- .gitpod.dockerfile
- .gitpod.yml
- CMakeLists.txt
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CodingGuidelines.md
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- DIRECTORY.md
- LICENSEGood: Licensed under MIT.
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- REVIEWER_CODE.md