92
/ 100
Polished and well engineered. Punching above its star count.
MCAP is a modular, performant, and serialization-agnostic container file format, useful for pub/sub and robotics applications.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 2Reproducibility6pt
Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.
- 3Dependency manifest6pt
Add a one-line description to package.json. It appears in npm search and on GitHub.
- 4Dependency manifest6pt
Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
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 MIT.
Engineering
99
Lockfile present (Cargo.lock). Installs are reproducible.
Test files detected (cpp/test).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (.prettierrc.yml).
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
- 38 / 78Commits (30d / 90d)
- 215Forks
- 101Releaseslatest 4y ago
Community
- 50% - FairCommunity health
- 4 bus factorauthors own >50% of commits
- 989Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 37Open issues
Repository files30 root entries
- .githubGood: CI is configured (.github/workflows/ci.yml).Good: Dependabot configured for github-actions.Good: Issue or PR templates present.
- .vscode
- cppGood: Test files detected (cpp/test).
- go
- pythonGood: Environment pinned via python/examples/ros2/Dockerfile.
- rust
- swift
- testdata
- tests
- typescript
- website
- .gitattributes
- .gitignoreGood: .gitignore present.
- .prettierignore
- .prettierrc.ymlGood: Linter or formatter configured (.prettierrc.yml).
- .swiftformat
- .swiftlint.yml
- .typos.toml
- .yarnrc.yml
- AGENTS.md
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- cspell.config.yaml
- LICENSEGood: Licensed under MIT.
- package.json
- Package.resolved
- Package.swift
- 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.
- RELEASING.md
- yarn.lock
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/foxglove/mcap)