Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

License issues in jna/native/libffi

Open
  • Is something wrong?
#1,691 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

Start by reviewing the files under jna/native/libffi and the attached jna_GPL export to identify the GPL-licensed components. Determine suitable replacements that avoid triggering copyleft for the rest of the repository, then verify the resulting tree with a license scan showing those GPL files are no longer present.

Written by the indexing model from the issue text.

Description

Hi, using your component I've performed a license scan an noticed that several files in jna/native/libffi come with a GPL, either 2.0 or 3.0. See the accompanying export from the license scanner. Could these files be replaced so copyleft is not triggered for the rest of the repo when distributing?

Cheers

jna_GPL export.txt

Dominant language
Java
Stars
8.9k
Forks
1.7k
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from java-native-access/jna

All issues in java-native-access/jna

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.