0
/ 100
Popular for its size, but the engineering basics lag behind the interest.
A web service offering HTML5 articles from arXiv.org as converted with latexml
Documentation
38
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
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 is present.
Licensed under MIT.
Engineering
73
No Cargo.lock found (−70 pts). Rust binary/application crates should commit Cargo.lock.
→ Run `cargo build` and commit the resulting Cargo.lock file.
Cargo.toml has dev-dependencies (may include test tooling).
CI is configured (.github/workflows/ci.yml).
Rust linting configured (cargo clippy in CI).
Issue or PR templates present.
Project health
86
Dependency manifest found (Cargo.toml).
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)
- 23Forks
- 3Releaseslatest 3y ago
Community
- -Community health
- -authors own >50% of commits
- 860Watchers
Responsiveness
- 30d 2hMedian issue response
- 4hMedian PR merge time
- 436Open issues
Repository files13 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot configured for cargo.Good: Issue or PR templates present.
- assets
- benches
- bin
- deploy
- src
- templates
- .gitignoreGood: .gitignore present.
- .rustfmt.toml
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- LICENSEGood: Licensed under MIT.
- 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 little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- Rocket.toml