nildyanna/armgddn-downloader
Grade a repo

0

/ 100

GradeF

Lots of room to improve. Start with a README and CI.

The new Armgddn App

Documentation44
Engineering33
Health92
JavaScript7today

Documentation

44

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.

README12pt50

README is present.

Install and run instructions9pt90

README documents how to install the project.

Engineering

33

Tests18pt0

No tests detected anywhere in the repository.

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

Linting and formatting5pt0

No linter or formatter found.

→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.

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.

Reproducibility6pt70

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

CI/CD14pt85

CI is configured (.github/workflows/build.yml).

Project health

92

Dependency manifest6pt75

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)
  • 2
    Forks
  • 343
    Releaseslatest 6mo ago

Community

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

Responsiveness

  • -
    Median issue response
  • 11h
    Median PR merge time
  • 0
    Open issues
Repository files32 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
  • .vscode
  • assets
  • build
  • mobile
  • openspec
  • renderer
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .markdownlint.json
  • .todo.md
  • AUTO_UPDATE_SETUP.md
  • BUILD_INSTRUCTIONS.md
  • CHANGELOG.md
  • CLAUDE.md
  • DEPLOYMENT.md
  • Disable-AutoUpdate-Using-DebugLog-Folder.bat
  • main.js
  • MANUAL_UNINSTALL.md
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • preload-update.js
  • preload.js
  • QUICK_START.md
  • RCLONE_SETUP.md
  • 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.
  • register-protocol.reg
  • SECURITY_AUDIT.md
  • SECURITY.md
    Good: Security policy present.
  • sync-version.js
  • UPDATE_TEST.txt
  • update-ed25519-pub.pem