Skip to content

A utility for managing cargo dependencies from the command line.

active 2025-01-182026-07-15 (UTC)

Partial coverage12,123 / 13,705 hourly files (88%) · 2 absent upstream · 1,578 failed, retryable2025-01-162026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
204
Pushes
6
Pull requests
5
Issues
11
Stars
141
Forks
9

Activity over time

Daily event counts in the loaded window

Line chart, 544 days from 2025-01-18 to 2026-07-15. Pushes: 6 total, peak 1 in a day. Pull requests: 5 total, peak 1 in a day. Issues: 11 total, peak 2 in a day. Comments: 27 total, peak 2 in a day. Stars: 141 total, peak 3 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue#963epage2026-06-07 01:32
    Value of adding a --cooldown option to delay adoption of crate versions
  • Issue#963epage2026-06-07 01:32
    Value of adding a --cooldown option to delay adoption of crate versions
  • Pull request#959epage2026-04-17 20:09
  • Issue#891epage2026-03-02 22:21
    Cargo `set-version --workspace` does not update `Cargo.lock` with private crate reference
  • Issue comment#958rmseq2026-03-02 21:07
    fix: propagate cargo metada errors instead of silent --no-deps fallback
  • Issue#957epage2026-02-02 13:32
    Feature request: Display a note if the `rust-version` field of the latest version of a dependent crate is incompatible
  • Issue#863epage2026-01-08 16:20
    Add `--allow-downgrade` option to set-version command
  • Issue comment#863DavidAntliff2025-12-02 23:07
    Add `--allow-downgrade` option to set-version command
  • Issue comment#952epage2025-10-29 13:41
    set-version: Add option to *not* change dependencies of other crates in workspace
  • Issue#952opara-tor2025-10-28 23:12
    set-version: Add option to *not* change dependencies of other crates in workspace
  • Issue comment#7492bndy52025-09-11 21:43
    Binary builds for each release?
  • Issue comment#950erenatas2025-09-11 06:13
    cargo upgrade requires index-url to have sparse
  • Issue#950erenatas2025-09-11 06:13
    cargo upgrade requires index-url to have sparse
  • Issue comment#863metasyn2025-09-04 17:41
    Add `--allow-downgrade` option to set-version command
  • Issue comment#950epage2025-09-02 13:39
    cargo upgrade requires index-url to have sparse
  • Issue comment#947epage2025-08-27 18:51
    `cargo install cargo-edit --no-default-features` fails to compile
  • Issue comment#853epage2025-08-08 14:35
    warning about yanked dependency crossbeam-channel v0.5.6
  • Pull request#944epage2025-08-05 20:37
  • Issue comment#944epage2025-08-05 20:23
    chore(deps): update dependencies
  • Issue comment#944epage2025-08-04 21:53
    chore(deps): update dependencies
  • Issue comment#863nullstalgia2025-07-31 04:01
    Add `--allow-downgrade` option to set-version command
  • Issue comment#946epage2025-07-17 19:13
    feat: incompatible prevents compatible upgrades
  • Issue comment#945epage2025-07-16 12:08
    Add command description to cargo --list
  • Issue comment#945G0rocks2025-07-16 11:36
    Add command description to cargo --list
  • Pull request#944reneleonhardt2025-07-15 14:54

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 141 stars here means stars gained during the window, not the repo's star count.