0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
A flexible, high-performance, user-friendly computer architecture simulator engine
Top fixes
Highest-impact changes first, ranked by point weight
- 1Install and run instructions9pt
Add a section showing how to start or use the project.
- 2Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 3Reproducibility6pt
Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.
- 4Issue and PR templates6pt
Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
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
69
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
86
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 (go.sum). Installs are reproducible.
Test files detected (daisen2/internal/httpapi/agentloop_test.go).
CI is configured (.github/workflows/akita_test.yml).
Formatting enforced (.golangci.yml).
Project health
100
Dependency manifest found (go.mod).
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)
- 28Forks
- 39Releaseslatest 2y ago
Community
- -Community health
- -authors own >50% of commits
- 108Watchers
Responsiveness
- 754d 23hMedian issue response
- 2hMedian PR merge time
- 21Open issues
Repository files30 root entries
- .githubGood: CI is configured (.github/workflows/akita_test.yml).
- .vscode
- akita
- daisen2Good: Test files detected (daisen2/internal/httpapi/agentloop_test.go).
- datarecording
- doc
- doc-site
- examples
- hooking
- internal
- memGood: Environment pinned via mem/dram/validation/oracles/Dockerfile.
- messaging
- modeling
- monitoring2
- naming
- noc
- queueing
- simulation
- sourcefs
- timing
- tracing
- .gitignoreGood: .gitignore present.
- .golangci.ymlGood: Formatting enforced (.golangci.yml).
- go.modGood: Dependency manifest found (go.mod).
- go.sumGood: Lockfile present (go.sum). Installs are reproducible.
- LICENSEGood: Licensed under MIT.
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- run_before_merge.sh
- TOOLCHAIN_VERSIONS.md
- TRACING_INSTRUMENTATION_PLAN.md
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/sarchlab/akita)