ahacker-1/cre-acquisition-orchestrator
Grade a repo

86

/ 100

GradeB

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

Top 20% of 5,156 graded repos

The first comprehensive open-source AI-native framework for CRE acquisitions, turning diligence, underwriting, financing, legal, and closing into executable agent workflows.

Documentation99
Engineering74
Health95
TypeScript82Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 to address
  1. 1
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  2. 2
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  3. 3
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  4. 4
    CI/CD14pt

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

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

99

Contributing guide5pt93

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

74

Linting and formatting5pt0

No linter or formatter found.

→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.

CI/CD14pt57

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

Reproducibility6pt70

Lockfile present (package-lock.json). Installs are reproducible.

Tests18pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

95

Dependency manifest6pt83

Dependency manifest found (package.json).

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)
  • 28
    Forks
  • 16
    Releaseslatest 2mo ago

Community

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

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 2
    Open issues
Repository files46 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • agents
  • config
  • dashboard
    Good: Test files detected (dashboard/e2e/a11y.spec.ts).
  • data
  • demo
  • docs
  • documents
  • eval
  • fixtures
  • orchestrators
  • schemas
  • scripts
  • skills
  • tasks
  • templates
  • validation
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AUDIT-BLOCKERS.md
  • AUDIT-PROGRESS.md
  • CHANGELOG.md
  • CITATION.cff
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • EVAL-PLAN.md
  • LAUNCH.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • NOTICE
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • RELEASE_NOTES_v1.1.0.md
  • RELEASE_NOTES_v2.0.0.md
  • RELEASE_NOTES_v2.1.0.md
  • RELEASE_NOTES_v2.2.0.md
  • RELEASE_NOTES_v2.3.0.md
  • RELEASE_NOTES_v2.4.0.md
  • RELEASE_NOTES_v2.5.0.md
  • RELEASE_NOTES_v2.6.0.md
  • RELEASE_NOTES_v3.0.0.md
  • RELEASE_NOTES_v3.1.0.md
  • RELEASE_NOTES_v3.2.0.md
  • RELEASE_NOTES_v3.3.0.md
  • ROADMAP.md
  • SECURITY.md
    Good: Security policy present.
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/ahacker-1/cre-acquisition-orchestrator)](https://www.repo-grade.com/report/ahacker-1/cre-acquisition-orchestrator)

More graded TypeScript repos