dcloudio/casecode

0

/ 100

Documentation38
Engineering60
Health85
JavaScript1,4471d ago
Grade a repo

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

DCloud开源项目集锦

Documentation

38

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.

README12pt18

README is present.

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

License6pt100

A license file is present.

Engineering

60

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 (hello-uni-app-x/code-review/__tests__).

Reproducibility6pt70

Lockfile present (hello-uni-app-x/code-review/package-lock.json). Installs are reproducible.

CI/CD14pt100

CI is configured (hello-uni-app-x/.gitlab-ci.yml).

Linting and formatting5pt100

Linter or formatter configured (hello-uni-app-x/.editorconfig).

Project health

85

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt72

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

  • —
    Commits (30d / 90d)
  • 846
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,447
    Watchers

Responsiveness

  • 39d 14h
    Median issue response
  • 3h
    Median PR merge time
  • 6
    Open issues
Repository files12 root entries
  • hello-uni-app-x
    Good: A license file is present.
    Good: Test files detected (hello-uni-app-x/code-review/__tests__).
    Good: CI is configured (hello-uni-app-x/.gitlab-ci.yml).
    Good: Linter or formatter configured (hello-uni-app-x/.editorconfig).
    Good: Lockfile present (hello-uni-app-x/code-review/package-lock.json). Installs are reproducible.
  • hello-uni-id-pages-x
  • hello-uts
  • hello-uvue
  • hellounicloud
    Issue: Build artifacts or local files may be committed (hellounicloud/pages/clientDB/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • share-fission-admin
  • share-fission-client
  • uni-ai-x
  • uni-app
  • .gitignore
    Good: .gitignore present.
  • 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.
    Issue: README has some structure (−7 pts). 2-3 headings earns partial credit; 4+ earns the full +15 pts.Fix: Add more sections (Overview, Install, Usage, Contributing) using ## headings.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.
    Good: README documents how to run the project.