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 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.
README is present.
README documents how to install the project.
A license file is present.
Engineering
78
CI is configured (.github/workflows/spellcheck-docs.yml).
Test files detected (packages/ably/jest.config.js).
Lockfile present (services/screenshots/requirements.txt). Installs are reproducible.
Linter or formatter configured (packages/live-previews/.prettierrc).
Issue or PR templates present.
Project health
94
.gitignore present.
Dependency manifest found (packages/ably/package.json).
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 96Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 687Watchers
Responsiveness
- 125d 12hMedian issue response
- 15hMedian PR merge time
- 3Open issues
Repository files20 root entries
- .githubGood: 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.
- configurationGood: A license file is present.Good: Environment pinned via configuration/docker/compose/1.0/docker-compose.yml.Good: .gitignore present.
- docker
- integrations
- opencli
- packagesGood: 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
- servicesGood: Lockfile present (services/screenshots/requirements.txt). Installs are reproducible.
- tests
- translations
- version
- website
- babel.cfg
- CONTRIBUTING.mdIssue: 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.mdGood: 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.mdGood: Security policy present.
- tsconfig.build.json