hzm0321/real-time-fund
Grade a repo

0

/ 100

GradeF

Strong community interest, but tests, CI, or docs need work.

Higher than 40% of 5,156 graded repos

基金实时估值查看

Documentation78
Engineering36
Health67
JavaScript1,395AGPL-3.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 B (81).

See your top fixes
Now
F
55
Potential
B
81

Top fixes

Highest-impact changes first, ranked by point weight

18 to address
  1. 1
    Tests18pt

    Add automated tests. They prove the code works and give contributors confidence to make changes.

  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

78

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

36

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

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.

CI/CD14pt57

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

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.json).

Project health

67

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt65

Dependency manifest found (package.json).

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 443
    Forks
  • 42
    Releaseslatest 5mo ago

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,395
    Watchers

Responsiveness

  • 17h
    Median issue response
  • 5h
    Median PR merge time
  • 23
    Open issues
Repository files40 root entries
  • .agent
  • .claude
  • .github
    Good: CI is configured (.github/workflows/docker-ci.yml).
  • .husky
  • .idea
    Issue: Build artifacts or local files may be committed (.idea/.gitignore) (−40 pts).Fix: Remove them and add to .gitignore.
  • .trae
  • .vercel
  • app
  • components
  • doc
  • lib
  • public
  • .dockerignore
  • .eslintrc.json
    Good: Linter or formatter configured (.eslintrc.json).
  • .gitignore
    Good: .gitignore present.
  • .prettierrc
  • .vercelignore
  • AGENTS.md
  • CLAUDE.md
  • components.json
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • entrypoint.sh
  • env.example
  • eslint.config.mjs
  • GEMINI.md
  • instrumentation-client.js
  • instrumentation.js
  • jsconfig.json
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • next.config.js
  • nginx.conf
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • postcss.config.mjs
  • 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.
  • sentry.edge.config.js
  • sentry.server.config.js
  • vercel.json
  • wrangler.jsonc
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/hzm0321/real-time-fund)](https://www.repo-grade.com/report/hzm0321/real-time-fund)

More graded JavaScript repos