yaomindong1996/forge-admin
Grade a repo

58

/ 100

GradeF

Getting some notice. Tests and CI would be the fastest wins.

Higher than 42% of 5,156 graded repos

AI编码，SpringBoot 3.x + JDK 17 构建的轻量化企业级管理系统基础框架，以配置驱动为核心设计理念，追求简洁高效、开箱即用，助力开发者快速搭建稳定可靠的企业级应用,极简开发、高效迭代、生产可用

Documentation84
Engineering33
Health79
Vue82Apache-2.01mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to A (90).

See your top fixes
Now
F
58
Potential
A
90

Top fixes

Highest-impact changes first, ranked by point weight

12 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

    If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

  3. 3
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

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

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

84

Contributing guide5pt0

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.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

33

CI/CD14pt0

No CI configuration detected in this repository.

→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.

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 (forge-admin-ui/src/components/flow-designer/__tests__).

Reproducibility6pt80

Lockfile present (forge-admin-ui/pnpm-lock.yaml). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (forge-admin-ui/eslint.config.js).

Project health

79

Dependency manifest6pt55

Dependency manifest found (package.json).

Housekeeping3pt60

.gitignore present.

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

  • -
    Commits (30d / 90d)
  • 30
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files27 root entries
  • .agents
  • .opencode
  • .qoder
  • code-copilot
    Good: Security policy present.
  • design-system
  • docker
    Good: Environment pinned via docker/docker-compose.yml.
  • docs
  • forge
  • forge-admin-ui
    Good: Test files detected (forge-admin-ui/src/components/flow-designer/__tests__).
    Good: Linter or formatter configured (forge-admin-ui/eslint.config.js).
    Good: Lockfile present (forge-admin-ui/pnpm-lock.yaml). Installs are reproducible.
  • forge-docs
  • forge-h5-ui
  • forge-report-ui
  • forge-server
  • images
  • output
  • scripts
  • .dockerignore
  • .DS_Store
    Issue: Build artifacts or local files may be committed (.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • CHANGELOG.md
  • FORGE_PRODUCTIZATION_PLAN.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • NGINX_CONFIG.md
  • package.json
    Good: Dependency manifest found (package.json).
  • README.en.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
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/yaomindong1996/forge-admin)](https://www.repo-grade.com/report/yaomindong1996/forge-admin)

More graded Vue repos