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

Continuously check 3rd party dependency license compatibility #39

Open
sophokles73 opened this issue Feb 9, 2024 · 1 comment
Open

Comments

@sophokles73
Copy link
Contributor

The Eclipse Foundation's development process requires us to make sure that the license terms of all 3rd party dependencies are compatible with the project's license (ASL2).

The first step in doing so is to actually determine the licenses that the 3rd party dependencies are using.

@AnotherDaniel
Copy link
Contributor

Question: how about we use cargo-deny for this, as a 'first line of defense' check that can be part of our direct build pipe? I know Eclipse has some larger system, which also will want to be satisfied - but I'm thinking that cargo-deny is a very nifty helper for a Rust project, for this kind of thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants