denchhq/denchclaw

Migrate to dench.com if you're reading this. Fully Managed OpenClaw Framework for all knowledge work ever. CRM Automation and Outreach agents. The only...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 41 minutes ago
Added to GitGenius on August 31st, 2026
Created on February 1st, 2026
Open Issues & Pull Requests: 96 (+0)
Number of forks: 126
Total Stargazers: 1,649 (+0)
Total Subscribers: 11 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.4 hours
Mean response time: 9.1 days
90th percentile: 50.7 days
Tracked items: 24

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 15% of open issues come from outside the core team — the tracker reads mainly as internal planning. 95% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 4% of issues opened in the past year have been closed. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 75
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 183 days
Stale 30+ days: 67
Stale 90+ days: 64

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (22)
  • enhancement (17)
  • security (14)
  • architecture (7)
  • testing (6)
  • dx (5)
  • performance (4)
  • documentation (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

I cannot provide a reliable summary of this repository. The README contains only a migration notice directing users to dench.com without describing the project's actual functionality, architecture, problem domain, or development approach. The description mentions CRM automation and outreach agents but provides no technical details about how the tool works, what distinguishes it from alternatives, or what adopters should know before choosing it. Without substantive information in the repository documentation itself, I cannot write an accurate summary that would remain true over time or help a developer make an informed adoption decision.