Good shape overall. A few tweaks would push it into the top tier.
URDF Loaders for Unity and THREE.js with example ATHLETE URDF Files open sourced from NASA JPL
Documentation
64
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
CONTRIBUTING guide found.
Licensed under Apache-2.0.
Engineering
77
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.
Lockfile present (javascript/package-lock.json). Installs are reproducible.
Test files detected (javascript/test).
CI is configured (.github/workflows/examples-build.yml).
Linter or formatter configured (javascript/.editorconfig).
Project health
100
Dependency manifest found (javascript/package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository files7 root entries
- .githubGood: CI is configured (.github/workflows/examples-build.yml).
- javascriptGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.Good: Test files detected (javascript/test).Good: Linter or formatter configured (javascript/.editorconfig).Good: Lockfile present (javascript/package-lock.json). Installs are reproducible.Good: Dependency manifest found (javascript/package.json).
- unity
- urdf
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under Apache-2.0.
- README.mdGood: README is present.Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.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.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.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.