Solid engineering. The main gap is visibility.

계단뿌셔클럽 서비스의 앱 코드 레포지토리

Documentation

82

README12pt70

README is present.

Contributing guide5pt74

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

Add setup instructions, code style notes, and how to run tests.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

70

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

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

Tests18pt80

Test files detected (__tests__).

Reproducibility6pt80

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

Linting and formatting5pt100

Linter or formatter configured (.eslintrc.js).

Project health

100

Dependency manifest6pt100

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)
  • 0
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files54 root entries
  • __tests__
    Good: Test files detected (__tests__).
  • .bundle
  • .claude
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/ci.yaml).
  • android
  • ios
  • patches
  • scripts
  • specs
  • src
  • subprojects
  • web
  • web-articles
  • .eslintignore
  • .eslintrc.js
    Good: Linter or formatter configured (.eslintrc.js).
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .node-version
    Good: Environment pinned via .node-version.
  • .prettierrc.js
  • .svgrrc
  • .tool-versions
  • .watchmanconfig
  • .yarnrc.yml
  • airbridge.json
  • app.json
  • App.tsx
  • babel.config.js
  • babel.config.web.js
  • CLAUDE.md
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    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.
    Good: Contributing guide includes code examples.
  • declaration.d.ts
  • DEPLOYMENT.md
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • global.css
  • global.d.ts
  • hot-updater.config.ts
  • index.js
  • jest.config.js
  • LICENSE.md
    Good: Licensed under Other.
  • metro.config.js
  • nativewind-env.d.ts
  • nativewind-migration.md
  • openapitools.json
  • package.json
  • postcss.config.js
  • 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.
    Good: README links to a live demo or deployed app.
    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.
  • tailwind.config.js
  • textFileTransformer.js
  • tsconfig.json
  • tsconfig.web.json
  • web-deploy.sh
  • webpack.config.js
  • yarn.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.