killercup/cargo-edit

A utility for managing cargo dependencies from the command line.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 20th, 2026
Created on June 18th, 2015
Open Issues & Pull Requests: 74 (+0)
GitHub issues: Enabled
Number of forks: 166
Total Stargazers: 3,454 (+0)
Total Subscribers: 15 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 23
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 548 days
Stale 30+ days: 19
Stale 90+ days: 15

Recent activity

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

Top labels

  • cargo-upgrade (19)
  • cargo-set-version (7)
  • enhancement (6)
  • bug (3)
  • breaking-change (1)
  • easy (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

cargo-edit is a command-line utility that extends Cargo to manage Rust project dependencies by adding, removing, and upgrading entries in Cargo.toml files.

The tool solves the problem of manually editing dependency declarations by providing subcommands that modify Cargo.toml directly from the terminal. It offers cargo upgrade to update dependencies to their latest versions, distinguishing itself from cargo update which only modifies the lock file. The tool also provides cargo set-version to change version numbers in Cargo.toml. Some functionality has been integrated into Cargo itself over time: cargo add became part of Cargo in version 1.62, and cargo rm in version 1.66, though the tool still provides these commands for users on older Cargo versions with some behavioral differences.

Developers maintaining projects on older Rust versions should consider installing cargo-edit to access add and rm functionality unavailable in their Cargo installation. The upgrade and set-version commands remain useful regardless of Cargo version. The README notes related tools like cargo-feature and cargo-override for complementary dependency management tasks but does not make direct comparisons to alternatives.

The project maintains a moderately comprehensive test suite and requires contributors to add tests for every change. Code contributions are expected to follow rustfmt formatting standards and pass clippy linting checks. The maintainers request that large changes be discussed in issues before submission and that pull requests and commits be kept short with clear intent in commit messages.