lilixu3/danmu-api-android

0

/ 100

Documentation66
Engineering39
Health94
Kotlin1691d ago
Grade a repo

Popular for its size, but the engineering basics lag behind the interest.

基于 huangxd-/danmu_api 的安卓 App：内置 Node.js，本机一键启用弹幕 API 服务

Documentation

66

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.

README12pt50

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

A license file is present.

Engineering

39

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.

Linting and formatting5pt0

No Java/Kotlin linter configured.

→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.

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.

Tests18pt80

Test files detected (app/src/test).

Reproducibility6pt80

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

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (build.gradle.kts).

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)
  • 10
    Forks
  • 72
    Releaseslatest 5mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 169
    Watchers

Responsiveness

  • 2h
    Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files12 root entries
  • announcement-center
    Good: Lockfile present (announcement-center/package-lock.json). Installs are reproducible.
    Good: Environment pinned via announcement-center/Dockerfile.
  • app
    Good: A license file is present.
    Good: Test files detected (app/src/test).
    Issue: Build artifacts or local files may be committed (app/src/main/assets/nodejs-project/config/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • docs
  • gradle
  • node-tests
  • .gitignore
    Good: .gitignore present.
  • build.gradle.kts
    Good: Dependency manifest found (build.gradle.kts).
  • gradle.properties
  • gradlew
  • gradlew.bat
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    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.
    Good: README has code examples.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • settings.gradle.kts