Good community traction and solid fundamentals. Nearly in the top tier.
Automatically tracks which apps you used, which websites you visited, and how much time you spent in each app throughout the day.
Documentation
82
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.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
65
No linter or formatter found.
→ Add ESLint (eslint.config.js) and/or Prettier (.prettierrc), install them as devDependencies, and add a `lint` script to package.json.
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 (Cargo.lock). Installs are reproducible.
Test files detected (Live2DRemoval.test.js).
Project health
89
Dependency manifest found (Cargo.toml).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 82Forks
- 52Releaseslatest 3mo ago
Community
- —Community health
- —authors own >50% of commits
- 1,362Watchers
Responsiveness
- 6hMedian issue response
- 1d 7hMedian PR merge time
- 1Open issues
Repository files29 root entries
- .githubGood: CI is configured (.github/workflows/release.yml).
- crates
- docs
- learning
- public
- scripts
- src
- src-tauri
- .gitignoreGood: .gitignore present.
- Cargo.lockGood: Lockfile present (Cargo.lock). Installs are reproducible.
- Cargo.tomlGood: Dependency manifest found (Cargo.toml).
- cargoToml.test.js
- CHANGELOG.md
- index.html
- LICENSEGood: Licensed under MIT.
- Live2DRemoval.test.jsGood: Test files detected (Live2DRemoval.test.js).
- package-lock.json
- package.json
- postcss.config.js
- 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.
- README.test.js
- README.tw.md
- README.zh.md
- releaseWorkflow.test.js
- svelte.config.js
- tailwind.config.js
- tauriDevHost.test.js
- THIRD_PARTY_NOTICES.md
- vite.config.js