Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False positive of local crate in a project's workspace #446

Closed
martingallagher opened this issue Aug 9, 2022 · 1 comment · Fixed by #520
Closed

False positive of local crate in a project's workspace #446

martingallagher opened this issue Aug 9, 2022 · 1 comment · Fixed by #520
Labels
bug Something isn't working

Comments

@martingallagher
Copy link

martingallagher commented Aug 9, 2022

Describe the bug
False positive of local crate in a project's workspace, this appears to first appear in 0.12.2

To Reproduce
Steps to reproduce the behavior:

  1. Clone https://github.com/martingallagher/cargodenybug
  2. Run cargo deny --workspace --all-features check
  3. Notice advisory regarding RUSTSEC-2020-0076

Expected behavior
In this instance the "routing" member of the workspace is vanilla Rust, it has no connection with any external crate so shouldn't raise a warning.

Device:

  • Version 0.12.2
@martingallagher martingallagher added the bug Something isn't working label Aug 9, 2022
@sbromling
Copy link

I have also seen this. It looks similar to #441, where a yanked-crate error was reported for a workspace-local crate of the same name.

In our case, we have a workspace-local crate called "generator", which has the same name as a public crate that has two active security advisories: https://rustsec.org/packages/generator.html.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants