Polished and well engineered. Punching above its star count.

An APP aimed at integrating various sources of campus information, developed with React Native

Documentation

93

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Other.

Engineering

84

CI/CD14pt57

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

Reproducibility6pt70

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

Tests18pt100

Test files detected (apps/thu-info-app/harmony/entry/src/ohosTest/ets/test).

Linting and formatting5pt100

Linter or formatter configured (apps/thu-info-app/.eslintrc.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

Dependency manifest found (Gemfile).

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)
  • 19
    Forks
  • 102
    Releaseslatest 5y ago

Community

  • Community health
  • authors own >50% of commits
  • 212
    Watchers

Responsiveness

  • 4h
    Median issue response
  • <1h
    Median PR merge time
  • 4
    Open issues
Repository files21 root entries
  • .bundle
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Issue or PR templates present.
  • .husky
  • apps
    Good: Test files detected (apps/thu-info-app/harmony/entry/src/ohosTest/ets/test).
    Good: Linter or formatter configured (apps/thu-info-app/.eslintrc.json).
  • packages
  • patches
  • .gitignore
    Good: .gitignore present.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • lerna.json
  • LICENSE
    Good: Licensed under Other.
  • package.json
  • PULL_REQUEST_TEMPLATE.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.
    Good: README documents how to run the project.
  • release-notes.md
  • renovate.json
  • SECURITY.md
    Good: Security policy present.
  • setup-harmony.sh
  • yarn.lock