71
/ 100
Solid engineering. The biggest lever is CI.
The AEC Open Source Directory - a curated directory of open source projects for the Architecture, Engineering, and Construction (AEC) industry.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
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
52
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.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
README is present.
Licensed under MIT.
Engineering
72
CI is configured (.github/workflows/rebuild-manual.yml).
Lockfile present (backend/pnpm-lock.yaml). Installs are reproducible.
Test files detected (backend/test).
Linter or formatter configured (backend/.prettierrc).
Issue or PR templates present.
Project health
100
Dependency manifest found (backend/package.json).
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)
- 5Forks
- 0Releases
Community
- 50% - FairCommunity health
- -authors own >50% of commits
- 33Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 6Open issues
Repository files8 root entries
- .githubGood: CI is configured (.github/workflows/rebuild-manual.yml).Good: Issue or PR templates present.
- backendGood: Test files detected (backend/test).Good: Linter or formatter configured (backend/.prettierrc).Good: Lockfile present (backend/pnpm-lock.yaml). Installs are reproducible.Good: Dependency manifest found (backend/package.json).
- docs
- frontend
- shared
- .gitignoreGood: .gitignore present.
- LICENSEGood: Licensed under MIT.
- README.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/opensource-construction/osc-directory)