est31

Current workaround: compile/cargo check for a target that is known to have no standard library. Also there is the issue that Cargo.toml doesn't contain any info that a crate is...

FTR, lib.rs has a list of git hashes corresponding to each release: https://lib.rs/crates/rodio/versions (click the "git" link). I'm a bit sad that this isn't exposed in neither crates.io or cargo,...

@Michael-F-Bryan as we've got other commands to influence cargo resolution like #4100 , I think the best place for integration is Cargo itself.

@fpoli the publication date is stored in git history, as in you have to find the commit that introduces the crate. Which is quite involved algorithmically and in time overhead...

@mathstuf that wouldn't detect yanked/unyanked crates. It seems that you can yank and un-yank crates arbitrarily often.

Hmmm nice it works from Github's API as well: ```` curl -i 'https://api.github.com/repos/est31/cargo-udeps/commits/master@\{2020-01-01\}' ```` It could be special cased for github with a fall back to a full clone of...

I have added a `WORKFLOW_TOKEN` token to the repository: 

> Currently I'm not sure that only the "Workflow RW rights" + "Metadata read" rights (as they appear in the screenshot) are enough for it to work - it could...

Lol, it's a bit confusing. @heyakyra if I read your request correctly, what you want is to create a JS application that behaves to the user like the current thing...

@heyakyra oh you are right, now I realize. This issue is different from #301. I originally got confused because I reported the single page question on another repo and it...