License notice and exception for frida-java-bridge 7.0.13
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation
Research direction
Start by checking package.json and the referenced Frida root COPYING at commit 63b3233f29c41fa274d634909cab7aaba81e4b32, then compare the exact 7.0.13 source and npm archives identified in the issue. Done means documenting or linking the authoritative copyright and LGPL exception notice applicable to redistribution, if the project can confirm it.
Written by the indexing model from the issue text.
Description
We are preparing a downstream compiled agent bundle using [email protected], corresponding to commit 6ab2a63e4b02ab881f11ea06632cebea4b1b435e.
The matching npm/source package.json declares LGPL-2.0 WITH WxWindows-exception-3.1. We could not locate a standalone LICENSE/COPYING/NOTICE or copyright statement in these exact archives.
Could you point us to the authoritative copyright/notice text and exception applicable to this release when redistributed in a compiled agent bundle? In particular, does Frida root COPYING at commit 63b3233f29c41fa274d634909cab7aaba81e4b32 apply to this bridge package, and what copyright notice should accompany it?
For exact identification, the npm tarball SHA-256 is 0ae4e5393b5bf237ba7cfe23666248a7e6884cc9321ac0a77f073bcb30d951c0.
Thank you for any existing release-specific documentation or notice file we should use.
- Dominant language
- JavaScript
- Stars
- 413
- Forks
- 173
- PR merge metrics
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from frida/frida-java-bridge
-
Types is missing `deoptimizeMethod`Possibly taken @Electric1447 claimed this 170 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 65/100
frida/frida-java-bridge#386 ·
-
[v7.0.11+] Process crash on accessing object["<init>"] with JVMTI availablePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
frida/frida-java-bridge#384 · 2 comments · 2 reactions ·
-
ensureClassInitialized() no longer initializes on ART since 7983e815 — hooks on uninitialized classes install successfully but never dispatchPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
frida/frida-java-bridge#408 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
frida/frida-java-bridge#404 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
frida/frida-java-bridge#397 · 2 comments ·
All issues in frida/frida-java-bridge
Similar issues
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
app bug config windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openai/codex#51926 · 2 comments ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-product-decision clawsweeper:needs-security-review clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:security issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openclaw/openclaw#166870 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
⚠ needs intervention document structure changed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
[Package] Widget primitives [Type] Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
WordPress/gutenberg#84204 · 1 comment ·
Maintainers usually reply within 1 day