PyGhidra Decaf
Java-free Python plugin loading for Ghidra
Enables pure Python Ghidra plugins to be implemented by handling the boilerplate JPype glue code to connect the Java and Python side plugin implementations.
Prerequisites
- Ghidra 11.0+ with PyGhidra installed (PyGhidra is included in the Ghidra distribution by default)
- Python 3.10+
Installation
- Activate (or create) the venv that will be used to run ghidra
- Install
pyghidra_decaf(pip install pyghidra_decaf) - Run ghidra
pyghidra --gui --install-dir /path/to/ghidra/install(for example ~/ghidra/ghidra_11_3_2_PUBLIC) - You'll be prompted to enable a new plugin, confirm that. If not, open File -> Install Extensions and enable "Pyghidra Decaf"
Installing Decaf plugins
- Activate the venv you previously set up with pyghidra_decaf
- Install the python module for the Decaf plugin (e.g.
pip install <your-decaf-plugin>) - Run ghidra
pyghidra --gui --install-dir /path/to/ghidra/install(for example ~/ghidra/ghidra_11_3_2_PUBLIC) - You'll be prompted to enable a new plugin, confirm that. If not, open File -> Install Extensions and enable "Pyghidra Decaf"
Troubleshooting
Plugin doesn't appear in Ghidra after installation
- Verify you're using Ghidra 11.0 or later. Older versions may not have PyGhidra bundled.
- Rerun
pyghidra --gui --install-dir /path/to/ghidra/installto trigger the bootstrap process. - Check that extension files were created:
ls -la ~/.config/ghidra/*/Extensions/
ImportError: jpype not found
- Ensure you're using the same Python virtual environment that Ghidra runs from. PyGhidra bundles JPype, but it must be loaded in the same venv context.
- Verify venv activation:
which pythonshould point to your plugin venv, not system Python.
Java class not found: myplugin.plugin.MyPlugin
- Verify the
decaf.loadentry point name matches your actual plugin class name. - The fully qualified name in the error message must match the first element of the tuple returned by your
decaf_load()function.
For more detailed help, see the Plugin Development Guide and Architecture Guide in the main repository.
1 maintainer
Metadata
1 maintainer
Release files for pyghidra-decaf 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pyghidra_decaf-0.3.1.tar.gz | 80.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyghidra_decaf-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 117.7 kB
Release files / pyghidra_decaf-0.3.1.tar.gz
| Download URL | pyghidra_decaf-0.3.1.tar.gz |
|---|---|
| Size | 80.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae4e7f51a6aea0d5ecd81aabc8c3c9e87ff9956446a8c63c34bb37dfecb47952
|
|
BLAKE2b-256 checksum How to use checksums |
ba1ab35e1d1edf6dcd3718642b5681e447c963b2108ff157091b5940ba0286fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 12, 2026.
Transparency logRelease files / pyghidra_decaf-0.3.1-py3-none-any.whl
| Download URL | pyghidra_decaf-0.3.1-py3-none-any.whl |
|---|---|
| Size | 37.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa6317157a5eee836325008537137600bd80f1673e50eb8413051f7b32f252f5
|
|
BLAKE2b-256 checksum How to use checksums |
f4f72dffc54c7375330db2e616d6ece499e3cdf8ef6b82fce6515928f84fec25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 12, 2026.
Transparency logSecurity for pyghidra-decaf 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pyghidra_decaf-0.3.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
