antfu-collective/taze

🥦 A modern cli tool that keeps your deps fresh

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 16th, 2026
Created on July 22nd, 2020
Open Issues & Pull Requests: 36 (+0)
GitHub issues: Enabled
Number of forks: 150
Total Stargazers: 4,284 (+1)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.2 days
Mean response time: 77.2 days
90th percentile: 369.4 days
Tracked items: 67

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 308 days
Stale 30+ days: 9
Stale 90+ days: 7

Recent activity

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

Top labels

  • enhancement (23)
  • pr welcome (9)
  • bug (2)
  • help wanted (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Taze is a command-line tool that keeps project dependencies up to date.

The tool addresses the common problem of managing dependency updates across projects. Rather than manually checking for new versions or relying on automated pull request services, Taze provides an interactive command-line interface that discovers available updates and helps developers decide which ones to apply. It works by scanning your project's dependency manifest, checking for newer versions, and presenting options for updating them selectively.

Taze suits developers who want direct control over their dependency update process without delegating to external services. It works well for projects where maintainers prefer to review and test updates locally before committing them, or for teams that need a lightweight tool integrated into their existing workflows. The interactive nature of the tool means you can update dependencies one at a time, skip certain packages, or batch updates as needed, rather than accepting all changes at once.

The project shows consistent maintenance with regular commits addressing bug fixes and feature improvements. Development activity demonstrates responsiveness to issues and pull requests, with updates flowing steadily into the codebase. The maintainers actively refine the tool based on user feedback and evolving dependency management needs.