We are preparing a downstream compiled agent bundle using frida-java-bridge@7.0.13, 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.
We are preparing a downstream compiled agent bundle using
frida-java-bridge@7.0.13, corresponding to commit6ab2a63e4b02ab881f11ea06632cebea4b1b435e.The matching npm/source
package.jsondeclaresLGPL-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
COPYINGat commit63b3233f29c41fa274d634909cab7aaba81e4b32apply 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.