klaudiosinani/tusk

Refined Evernote desktop app

View on GitHub ↗Jump to charts ↓

klaudiosinani/tusk has 3k+ stars and 200+ forks on GitHub, is written in JavaScript, and was last pushed on Jun 24, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 22nd, 2026
Created on August 7th, 2017
Open Issues & Pull Requests: 191 (+0)
GitHub issues: Enabled
Number of forks: 241
Total Stargazers: 3,155 (+0)
Total Subscribers: 81 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 65.5 days
Mean response time: 257.1 days
90th percentile: 875.5 days
Tracked items: 19

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,174 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

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

Top labels

  • duplicate (12)
  • bug (3)
  • invalid (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Tusk is a desktop application that provides a refined interface for Evernote. The tool wraps the Evernote web experience in a native desktop container, applying visual and functional improvements to the standard Evernote interface. It addresses the limitations of Evernote's official desktop client by offering a cleaner, more polished user experience while maintaining full access to Evernote's core functionality through its web platform.

Developers and power users of Evernote who find the official client lacking in polish or responsiveness may benefit from Tusk's streamlined approach. The tool suits anyone who prefers a lightweight desktop wrapper over the heavier official Evernote application, particularly those working on systems where resource efficiency matters. It is especially relevant for users who spend significant time in Evernote and value interface refinement and customization options that the standard client does not provide.

The project maintains active development with regular updates and responsiveness to user contributions. The codebase shows consistent engagement with pull requests being reviewed and merged, indicating an actively maintained tool rather than an abandoned experiment. Development activity demonstrates a pattern of incremental improvements and bug fixes applied to the codebase over time.