Skip to content

Is the libfuzzer license information still accurate? #130

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

Open
hanna-kruppe opened this issue Feb 1, 2025 · 2 comments
Open

Is the libfuzzer license information still accurate? #130

hanna-kruppe opened this issue Feb 1, 2025 · 2 comments

Comments

@hanna-kruppe
Copy link

hanna-kruppe commented Feb 1, 2025

The SPDX expression is "(MIT OR Apache-2.0) AND NCSA" and the README says:

All files in the libfuzzer directory are licensed NCSA.

Everything else is dual-licensed Apache 2.0 and MIT.

But the vendored version of libfuzzer is from LLVM 19.x, long after LLVM started relicensing from NCSA to Apache-2.0 WITH LLVM-exception. There doesn't seem to be any definite statement whether the relicensing is 100% complete, but it's pretty far along:

  1. Some rust-lang projects have updated their license strings in line with the new LLVM license, dropping NCSA (e.g., Update licensing to MIT AND Apache-2.0 WITH LLVM-exception rust-lang/compiler-builtins#717)
  2. Since 2024-06-01, LLVM upstream no longer requires new contributions to be dual-licensed under NCSA and Apache-2.0 WITH LLVM-exception. The currently vendored commit includes some changes to libfuzzer made since then, which presumably aren't licensed under NCSA at all.

I'm no licensing expert but it seems like NCSA should be replaced with Apache-2.0 WITH LLVM-exception in Cargo.toml and README.

@fitzgen
Copy link
Member

fitzgen commented Feb 27, 2025

I'm no licensing expert either but your explanation makes sense to me.

@Manishearth
Copy link
Member

I think that's fine

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

3 participants