farzaa / clicky
Repository health
Security advisories, maintenance activity, dependencies and license for farzaa/clicky, with what was checked and what was not.
Security
51 dependencies checked (1 direct), npm, via deps.dev. Findings apply only to the packages and versions checked.
OpenSSF Scorecard · 2.3/10
Checks sorted from strongest to weakest.
- LicensePermissive license: MIT10/10
- MaintainedLast commit 168d ago6/10
- Code-ReviewOnly 0/20 recent PRs had requested reviewers2/10
- CI-TestsNo CI workflows detected0/10
- Dependency-Update-ToolNo Dependabot or Renovate config found0/10
- Security-PolicyNo SECURITY.md found0/10
- SASTNo SAST workflow detected0/10
- Branch-ProtectionDefault branch 'main' has no protection rule0/10
- Token-PermissionsNo workflows to inspectnot scored
- Pinned-DependenciesNo workflows to inspectnot scored
Maintenance
Outside contributions: 0 of 90 external pull requests merged (0% of those decided).From the 90 most recently updated pull requests, bots excluded.
Commit activity
20 commits sampledClick a bar to browse commits — or open GitHub for the full month ↓
Work rhythm
Commits by day of week
Pull request health
How fast do PRs resolve?
Days from open to merged / closed, last 17 PRs.
Pending right now13 open PRs
⚠ 6 stale PRs — open more than 60 days, no update in 30+
Long-running PRs without recent activity are usually maintainer-bandwidth signals — review process bottleneck, orphaned branches, or quietly abandoned work.
Issue triage — last 12 weeks
Blue bars = issues opened that week, green = closed. Healthy projects keep these roughly in balance — a persistently bigger blue bar means an opening backlog. open issues on GitHub ↗
Top contributors
Issue health
Computed from GitHub Issues — no estimates. Per-issue rates use the 26 most-recently-updated issues (recent, not all-time); the open total and oldest-open age are repo-wide.
Total open on the repo (authoritative).
From 0 recently-closed issues. p90 —.
Age of the longest-open unresolved issue.
12 of 26 recent open issues have no comments yet.
25 of 26 recent open issues had no update in 30d+.
26 of 26 recent open issues are unlabeled.
What the backlog is about
AI-generatedOpen issues grouped into themes by an LLM from their titles — a summary, not an authoritative classification. Numbers reflect the 26 most-recently-active open issues.
Most-wanted
Open issues with the most positive reactions — what the community is asking for.
add Windows version
#21 · opened 6mo ago · @musketyr
Critical Security Issues
#44 · opened 6mo ago · @Breadarr5
For windows
#63 · opened 6mo ago · @khanrohittt7878-stack
Windows companion app — open source Electron rewrite
#26 · opened 6mo ago · @tekram
Built a Linux version of Clicky
#59 · opened 6mo ago · @tornikegomareli
Most-discussed
Open issues with the most comments — where the conversation is.
Windows companion app — open source Electron rewrite
#26 · opened 6mo ago · @tekram
For windows
#63 · opened 6mo ago · @khanrohittt7878-stack
Running out of credit - how can I use my own codex or claude code API key?
#27 · opened 6mo ago · @EvHanHan
add Windows version
#21 · opened 6mo ago · @musketyr
Persistent memory across sessions — proposal to integrate TINM as MCP backend
#93 · opened 5mo ago · @momo590
Per-issue rates are computed from a sample of 26 most-recently-updated issues, so they describe recent behavior rather than the all-time backlog. Reaction and comment counts come straight from GitHub.
Dependencies
Checked packages and import counts
Checked counts describe advisory coverage, not the repository’s complete dependency inventory. External imports come from a separate source-code graph.