87
/ 100
Well engineered for its size. A portfolio piece worth showing off.
Agentic research control plane: queue state, worker preflight, wake-gated execution, evidence sync, dashboard, alerts, and AI-generated paper packaging.
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.
- 2README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 3Install and run instructions9pt
Add a .env.example listing all required environment variables so contributors know what to set up.
- 4Contributing guide5pt
Add setup instructions, code style notes, and how to run tests.
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
86
CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
README documents how to install the project.
Licensed under Other.
Engineering
82
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
Test files detected (dashboard/e2e/dashboard.spec.ts).
CI is configured (.github/workflows/build.yml).
Lockfile present (uv.lock). Installs are reproducible.
Issue or PR templates present.
Project health
100
Dependency manifest found (pyproject.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)
- 2Forks
- 256Releaseslatest 2mo ago
Community
- 85% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 16Watchers
Responsiveness
- 15hMedian issue response
- <1hMedian PR merge time
- 3Open issues
Repository files38 root entries
- .agents
- .cursor
- .devcontainerGood: Environment pinned via .devcontainer/Dockerfile.
- .githubGood: CI is configured (.github/workflows/build.yml).Good: Dependabot covers 2 ecosystems (github-actions, pip). Dependencies stay current.Good: Issue or PR templates present.
- .semgrep
- .vscode
- artifacts
- codex-skills
- dashboardGood: Test files detected (dashboard/e2e/dashboard.spec.ts).
- deploy
- docs
- enoch_control_plane
- paper_templates
- scripts
- site
- supabase
- targeted_paper_intakes
- tests
- .gitignoreGood: .gitignore present.
- .gitleaksignore
- .pre-commit-config.yaml
- .zap-rules.tsv
- AGENTS.md
- CHANGELOG.md
- CODEOWNERS
- config.example.json
- CONTRIBUTING.mdIssue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- docker-compose.yml
- LICENSEGood: Licensed under Other.
- Makefile
- NOTICE
- pyproject.tomlGood: Dependency manifest found (pyproject.toml).
- pyrightconfig.ci.json
- 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.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.Good: README documents how to install the project.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
- sonar-project.properties
- uv.lockGood: Lockfile present (uv.lock). Installs are reproducible.
- VERSION
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/alias8818/enoch-agentic-research-system)