Getting some notice. Tests and CI would be the fastest wins.
A feature-rich clipboard manager for GNOME Shell that integrates clipboard history, an emoji picker with skin-tone support, GIF search, and extensive kaomoji/symbol libraries into a single, unified panel.
Documentation
89
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under GPL-3.0.
Engineering
30
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
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 (package-lock.json). Installs are reproducible.
Linter or formatter configured (.prettierrc).
Project health
94
Dependency manifest found (package.json).
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)
- 12Forks
- 24Releaseslatest 7mo ago
Community
- —Community health
- —authors own >50% of commits
- 88Watchers
Responsiveness
- 18hMedian issue response
- 13hMedian PR merge time
- 9Open issues
Repository files19 root entries
- .githubGood: CI is configured (.github/workflows/release.yml).
- build
- gnome-extensions
- server
- .gitignoreGood: .gitignore present.
- .gitlab-ci.yml
- .prettierignore
- .prettierrcGood: Linter or formatter configured (.prettierrc).
- .stylelintrc.json
- build.sh
- CONTRIBUTING.mdGood: 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.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.
- eslint.config.js
- EXCLUSIONS.md
- install.sh
- LICENSEGood: Licensed under GPL-3.0.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- 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.
- uninstall.sh