A top-tier open source project. Docs, tests, and CI are all in excellent shape.
Create book from markdown files. Like Gitbook but implemented in Rust
Documentation
85
README is present.
README documents how to install the project.
Licensed under MPL-2.0.
Contributing guide is detailed and thorough.
Engineering
96
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (tests).
CI is configured (.github/workflows/main.yml).
Linter or formatter configured (eslint.config.mjs).
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
- 9 / 28Commits (30d / 90d)
- 1,862Forks
- 102Releaseslatest 10y ago
Community
- 75% - GoodCommunity health
- 3 bus factorauthors own >50% of commits
- 21,863Watchers
Responsiveness
- 14d 3hMedian issue response
- 2hMedian PR merge time
- 691Open issues
Repository files22 root entries
- .cargo
- .githubGood: CI is configured (.github/workflows/main.yml).Good: Issue or PR templates present.
- ci
- crates
- examples
- guide
- src
- testsGood: Test files detected (tests).
- .git-blame-ignore-revs
- .gitattributes
- .gitignoreGood: .gitignore present.
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- CHANGELOG.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CONTRIBUTING.mdGood: Contributing guide is detailed and thorough.Good: Contributing guide includes setup/install instructions.Good: Contributing guide describes code style expectations.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- LICENSEGood: Licensed under MPL-2.0.
- package.json
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- rustfmt.toml
- triagebot.toml