Kevin K.

That is strange, thanks for reporting. I'll keep an eye out and report back if I find something to fix this!

Postponed until #4 is solved

### Update I'm not worried about requiring **nightly** `rustc` anymore. `cargo-clippy` was actually briefly included with this package...but prematurely so. It installed and compiled just fine, but turns out actually...

Absolutely! Would you like to create `cargo-dybuk` project, or just boulder dybuk as is and rename the binary to `cargo-dybuk` from this repo? (Haven't tested the latter, but I'm assuming...

Sounds great, once you've got it read let me know and I'll include and put out a new release! :+1:

Parsing local modules probably wouldn't be too difficult, but parsing external modules (to include `std`) would be much more difficult and require the source. I'll play with some ideas and...

I'm not familiar with this, could you elaborate or point a link for this? I did some quick googling, if you've got something specific I'd be interested to see it.

What distro are you using? It could be the root certificates were not yet installed, but after installing `rust` and `cargo` they were picked up?

Ah cool idea! It may be little bit of time before I can work on this, but I like the idea and will see how it looks as I dig...

The issue for `cargo-outdated` is only direct wild cards can be determined, because it uses the `Cargo.lock` to find versions, not the original crates `Cargo.toml`. I'm not against adding this,...