wenxig/dongtai-sub
Grade a repo

0

/ 100

GradeF

Getting noticed, but rough fundamentals could turn visitors away.

Higher than 34% of 5,156 graded repos

科学上网: 免费！✈️✈️✈️自动抓取Alvin9999的节点🪜🪜🪜，已适配账号迁移🪜🪜🪜，多格式支持。✈️✈️✈️，，，，chatgpt，gemini，claude，grok，x，twitter，youtube，油管，discord，google，yandex，tor，github，代理，节点，梯子，fanqiang

Documentation30
Engineering45
Health86
TypeScript1841mo 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 C (70).

See your top fixes
Now
F
48
Potential
C
70

Top fixes

Highest-impact changes first, ranked by point weight

23 to address
  1. 1
    Tests18pt

    Add a scripts.test entry and create your first test file.

  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 `pull_request:` to the workflow `on:` triggers.

  4. 4
    CI/CD14pt

    Add a lint step to catch style issues automatically.

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

30

Install and run instructions9pt0

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

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.

README12pt80

README is present.

Engineering

45

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.

Tests18pt40

A test framework is installed but no test script or test files were found.

→ Add a scripts.test entry and create your first test file.

CI/CD14pt40

CI is configured (.github/workflows/hourly-write.yml).

Reproducibility6pt70

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

Linting and formatting5pt100

Linter or formatter configured (devDependency in package.json).

Project health

86

Dependency manifest6pt55

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)
  • 22
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 184
    Watchers

Responsiveness

  • 10d 7h
    Median issue response
  • <1h
    Median PR merge time
  • 0
    Open issues
Repository files11 root entries
  • .github
    Good: CI is configured (.github/workflows/hourly-write.yml).
  • data
  • src
  • .gitignore
    Good: .gitignore present.
  • .oxfmtrc.json
  • .oxlintrc.json
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • clash_template.yaml
  • package.json
    Good: Dependency manifest found (package.json).
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • tsconfig.json
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/wenxig/dongtai-sub)](https://www.repo-grade.com/report/wenxig/dongtai-sub)

More graded TypeScript repos