azurite-bedrock/universal-language-pack
Grade a repo

0

/ 100

GradeF

Getting some notice. Tests and CI would be the fastest wins.

Adds new Translations to Minecraft Bedrock Edition

Documentation61
Engineering51
Health68
TypeScript10today

Documentation

61

License6pt0

No license detected.

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

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt67

Contributing guide is detailed and thorough.

README12pt100

README is present.

Engineering

51

Reproducibility6pt0

No dependency lockfile found (−70 pts).

→ Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.

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/CD14pt40

CI is configured (.github/workflows/build-and-release.yml).

Tests18pt80

Test files detected (scripts/banner-stats.test.ts).

Linting and formatting5pt100

Linter or formatter configured (.prettierrc.json).

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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)
  • 1
    Forks
  • 59
    Releaseslatest 11mo ago

Community

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

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files15 root entries
  • .github
    Good: CI is configured (.github/workflows/build-and-release.yml).
  • .vscode
  • assets
  • LICENSES
  • locales
  • packs
  • scripts
    Good: Test files detected (scripts/banner-stats.test.ts).
  • .gitignore
    Good: .gitignore present.
  • .prettierrc.json
    Good: Linter or formatter configured (.prettierrc.json).
  • config.json
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • handled-versions.json
  • NOTICE.md
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • TRADEMARK.md