Picks up dependencies from other crates

[epage]

Note: this is purely from code inspection

It looks like if I ran this in a workspace root where a crate is in the root, it will search all other crates within the workspace

You can use cargo package --list to see what will be put on crates.io. The downside is people might exclude files related to dev-dependencies, like tests.

[bnjbvr]

That's correct, but I would call it a feature? :p Basically the ability to run machete in any directory that contains any crates, and one could still filter out uninteresting results (assuming #13).