Just launched. Good start. Add tests and CI early.
Send files between machines. No accounts, no root, no install. E2E encrypted.
Documentation
92
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 documents how to install the project.
README is present.
Licensed under MIT.
Engineering
20
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
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 is configured (.github/workflows/release.yml).
Lockfile present (tubo-cli/go.sum). Installs are reproducible.
Project health
100
Dependency manifest found (server/pom.xml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- 13 / 13Commits (30d / 90d)
- 0Forks
- 1Releaseslatest 2d ago
Community
- 75% - GoodCommunity health
- 1 bus factorlowauthor own >50% of commits
- 1Watchers
Responsiveness
- —Median issue response
- —Median PR merge time
- 0Open issues
Repository files11 root entries
- .githubGood: CI is configured (.github/workflows/release.yml).
- docs
- serverGood: Dependency manifest found (server/pom.xml).
- tubo-cliGood: Lockfile present (tubo-cli/go.sum). Installs are reproducible.
- .gitignoreGood: .gitignore present.
- 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).Good: Contributing guide describes the PR/review workflow.Good: Contributing guide includes code examples.
- install.sh
- LICENSEGood: Licensed under MIT.
- 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.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- run.sh
- SECURITY.mdGood: Security policy present.