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

A highly customizable web hosting control panel built around containers

Documentation

86

Contributing guide5pt53

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.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

A license file is present.

Engineering

78

CI/CD14pt57

CI is configured (.github/workflows/spellcheck-docs.yml).

Tests18pt80

Test files detected (packages/ably/jest.config.js).

Reproducibility6pt80

Lockfile present (services/screenshots/requirements.txt). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (packages/live-previews/.prettierrc).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (packages/ably/package.json).

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

Community

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

Responsiveness

  • 125d 12h
    Median issue response
  • 15h
    Median PR merge time
  • 3
    Open issues
Repository files20 root entries
  • .github
    Good: CI is configured (.github/workflows/spellcheck-docs.yml).
    Good: Issue or PR templates present.
    Issue: Build artifacts or local files may be committed (.github/.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • configuration
    Good: A license file is present.
    Good: Environment pinned via configuration/docker/compose/1.0/docker-compose.yml.
    Good: .gitignore present.
  • docker
  • integrations
  • opencli
  • packages
    Good: Test files detected (packages/ably/jest.config.js).
    Good: Linter or formatter configured (packages/live-previews/.prettierrc).
    Good: Dependency manifest found (packages/ably/package.json).
  • patches
  • services
    Good: Lockfile present (services/screenshots/requirements.txt). Installs are reproducible.
  • tests
  • translations
  • version
  • website
  • babel.cfg
  • 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.
    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).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • cspell.json
  • install.sh
  • OLD_install.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.
    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.
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.build.json