churchapps/b1admin

0

/ 100

Documentation75
Engineering67
Health89
TypeScript136MIT1d ago
Grade a repo

Good shape overall. A few tweaks would push it into the top tier.

Church Management Software

Documentation

75

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.

README12pt75

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

67

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/submodule-sync.yml).

Reproducibility6pt70

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

Tests18pt100

Test files detected (tests).

Linting and formatting5pt100

Linter or formatter configured (eslint.config.js).

Project health

89

Dependency manifest6pt65

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)
  • 56
    Forks
  • 27
    Releaseslatest 5y ago

Community

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

Responsiveness

  • —
    Median issue response
  • <1h
    Median PR merge time
  • 1
    Open issues
Repository files24 root entries
  • .github
    Good: CI is configured (.github/workflows/submodule-sync.yml).
  • .tx
  • .vscode
  • public
  • src
  • tests
    Good: Test files detected (tests).
  • types
  • .dockerignore
  • .env.sample
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .yarnrc.yml
  • eslint.config.js
    Good: Linter or formatter configured (eslint.config.js).
  • index.html
  • LICENSE
    Good: Licensed under MIT.
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.ts
  • railway.json
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
  • tsconfig.app.json
  • tsconfig.json
  • tsconfig.node.json
  • vite.config.ts
  • yarn.lock
    Good: Lockfile present (yarn.lock). Installs are reproducible.