Popular for its size, but the engineering basics lag behind the interest.
Taylor polynomial expansions in one and several independent variables.
Documentation
85
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under Other.
Engineering
46
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.
CI is configured (.github/workflows/ci.yml).
Test files detected (test).
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)
- 54Forks
- 88Releaseslatest 7y ago
Community
- —Community health
- —authors own >50% of commits
- 367Watchers
Responsiveness
- 2hMedian issue response
- 3d 22hMedian PR merge time
- 23Open issues
Repository files14 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).
- docs
- examples
- ext
- paper
- perf
- src
- testGood: Test files detected (test).
- .gitignoreGood: .gitignore present.
- CITATION.bib
- CITATION.cff
- LICENSE.mdGood: Licensed under Other.
- Project.toml
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.