steedos/steedos-platform
Grade a repo

71

/ 100

GradeC

Good community traction and solid fundamentals. Nearly in the top tier.

Top 45% of 5,156 graded repos

The AI-Native Infrastructure for Enterprise Apps. Powered by ObjectStack (ObjectQL, ObjectOS, Object UI). Turn Prompts into Enterprise Software.

Documentation96
Engineering49
Health83
TypeScript1,563AGPL-3.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

17 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

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

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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

96

Contributing guide5pt76

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

49

Issue and PR templates6pt0

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.

Tests18pt35

Test files detected (builder6/ai/src/ai/ai.service.spec.ts).

CI/CD14pt57

CI is configured (.github/workflows/npm-release.yml).

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (eslint.config.mjs).

Project health

83

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt65

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 26 / 230
    Commits (30d / 90d)
  • 415
    Forks
  • 1000
    Releaseslatest 4y ago

Community

  • 50% - Fair
    Community health
  • 2 bus factor
    authors own >50% of commits
  • 1,563
    Watchers

Responsiveness

  • 7d 16h
    Median issue response
  • 413d 2h
    Median PR merge time
  • 578
    Open issues
Repository files38 root entries
  • .github
    Good: CI is configured (.github/workflows/npm-release.yml).
  • .vscode
  • .yarn
  • builder6
    Good: Test files detected (builder6/ai/src/ai/ai.service.spec.ts).
    Issue: Build artifacts or local files may be committed (builder6/server/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • deploy
    Good: Environment pinned via deploy/cluster/docker-compose.yml.
  • docs
  • ee
  • packages
  • services
  • skills
  • test
  • .commitlintrc.json
  • .cursorrules
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .prettierignore
  • .yarnclean
  • .yarnrc.yml
  • CODE_OPTIMIZATION_SUGGESTIONS.md
  • CODE_QUALITY_ANALYSIS.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • eslint.config.mjs
    Good: Linter or formatter configured (eslint.config.mjs).
  • EXPLORATION_SUMMARY.txt
  • lerna.json
  • LICENSE.txt
    Good: Licensed under AGPL-3.0.
  • package.json
    Good: Dependency manifest found (package.json).
  • PUBLISH.md
  • QUICK_ACTION_ITEMS.md
  • QUICK_REFERENCE.md
  • README_cn.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.
  • README.md
  • SPEC_INDEX.md
  • SPEC_VALIDATION_SUMMARY.md
  • START_HERE.md
  • STEEDOS_SPEC_REFERENCE.md
  • steedos.config.js
  • tsconfig.json
  • yarn.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.
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/steedos/steedos-platform)](https://www.repo-grade.com/report/steedos/steedos-platform)

More graded TypeScript repos