Popular for its size, but the engineering basics lag behind the interest.
A Julia package to construct orthogonal polynomials, their quadrature rules, and use it with polynomial chaos expansions.
Documentation
66
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.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
48
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 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.
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/Tests.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)
- 26Forks
- 18Releaseslatest 4y ago
Community
- —Community health
- —authors own >50% of commits
- 122Watchers
Responsiveness
- 5hMedian issue response
- 4hMedian PR merge time
- 14Open issues
Repository files10 root entries
- .githubGood: CI is configured (.github/workflows/Tests.yml).Good: Dependabot covers 2 ecosystems (github-actions, julia). Dependencies stay current.
- docs
- examples
- src
- testGood: Test files detected (test).
- .gitignoreGood: .gitignore present.
- .typos.toml
- LICENSE.mdGood: Licensed under MIT.
- Project.toml
- README.mdGood: README is present.Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.