{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicqpgt7drgmwydrpxoha2yvaiizv2qvwcbouke2hgeqt3a6liavfq",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mfkdxviug2p2"
  },
  "path": "/t/child-thread-survey-of-alternative-identifier-designs-for-cargo-and-crates-io/24029#post_7",
  "publishedAt": "2026-02-23T14:11:54.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "dlight:\n\n> But now I think about it, a third-party tool (or even a first party cargo subcommand) that lists actively maintained forks of abandoned dependencies of your project might be a good replacement, at least for people that actually bother to use such a tool (there would still be churn though).\n\nThis already exists: `cargo-deny`/`cargo-audit`.",
  "title": "Child Thread: Survey of alternative identifier designs for Cargo and Crates.io"
}