87

/ 100

GradeB

Well engineered for its size. A portfolio piece worth showing off.

Top 18% of 5,156 graded repos

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

10 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  3. 3
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  4. 4
    Contributing 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.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

86

Contributing guide5pt55

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

82

Linting and formatting5pt0

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.

Tests18pt80

Test files detected (dashboard/e2e/dashboard.spec.ts).

CI/CD14pt100

CI is configured (.github/workflows/build.yml).

Reproducibility6pt100

Lockfile present (uv.lock). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pyproject.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 2
    Forks
  • 256
    Releaseslatest 2mo ago

Community

  • 85% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 16
    Watchers

Responsiveness

  • 15h
    Median issue response
  • <1h
    Median PR merge time
  • 3
    Open issues
Repository files38 root entries
  • .agents
  • .cursor
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: 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
  • dashboard
    Good: Test files detected (dashboard/e2e/dashboard.spec.ts).
  • deploy
  • docs
  • enoch_control_plane
  • paper_templates
  • scripts
  • site
  • supabase
  • targeted_paper_intakes
  • tests
  • .gitignore
    Good: .gitignore present.
  • .gitleaksignore
  • .pre-commit-config.yaml
  • .zap-rules.tsv
  • AGENTS.md
  • CHANGELOG.md
  • CODEOWNERS
  • config.example.json
  • CONTRIBUTING.md
    Issue: 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
  • LICENSE
    Good: Licensed under Other.
  • Makefile
  • NOTICE
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • pyrightconfig.ci.json
  • README.md
    Good: 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.md
    Good: Security policy present.
  • sonar-project.properties
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.
  • VERSION
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/alias8818/enoch-agentic-research-system)](https://www.repo-grade.com/report/alias8818/enoch-agentic-research-system)

More graded Python repos