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

eCamp v3 is a web-based app for camp and course planning. The application is specialized for camps and courses of youth associations and for Y+S offers in the sport of camp sports/trekking.

Documentation

91

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under AGPL-3.0.

Engineering

61

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.

Tests18pt35

Test files detected (.helm/ecamp3/templates/tests).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (.github/workflows/check-dependencies.yml).

Linting and formatting5pt100

Linter or formatter configured (.ops/aws-setup/eslint.config.mjs).

Project health

79

Dependency manifest6pt55

Dependency manifest found (package.json).

Housekeeping3pt60

.gitignore present.

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 67
    Forks
  • 19
    Releaseslatest 1y ago

Community

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

Responsiveness

  • 43d
    Median issue response
  • 7h
    Median PR merge time
  • 235
    Open issues
Repository files43 root entries
  • .agents
    Good: Environment pinned via .agents/.ecamp/playwright-cli/Dockerfile.
    Good: .gitignore present.
  • .cache
  • .docker-hub
  • .github
    Good: CI is configured (.github/workflows/check-dependencies.yml).
  • .helm
    Good: Test files detected (.helm/ecamp3/templates/tests).
  • .ops
    Good: Linter or formatter configured (.ops/aws-setup/eslint.config.mjs).
  • .playwright
  • .vscode
  • api
    Issue: Build artifacts or local files may be committed (api/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • common
  • e2e
  • frontend
  • frontend-old
  • pdf
  • print
  • translation
  • .claude
  • .dockerignore
  • .env.ci
  • .gitattributes
  • .gitignore
  • .nvmrc
  • .opencode
  • .prettierignore
  • .prettierrc
  • AGENTS.md
  • CLAUDE.md
  • CONTRIBUTING_DE.md
  • 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.
    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.
  • create-ecamp3-test-database.sh
  • crowdin.yml
  • docker-compose.override.yml
  • docker-compose.yml
  • docker-setup.sh
  • LICENSE
    Good: Licensed under AGPL-3.0.
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • pgadmin-servers.json
  • pre-commit.sh
  • 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • renovate.json
  • reverse-proxy-nginx.conf
  • wait-for-container-startup.sh