Migrate "params" from core to an add-on
Open
@kingthorin is already working on this.
Since Jan 6, 2026.
add-on
Maintainability
tracker
Usability
- Dominant language
- Java
- Stars
- 15.8k
- Forks
- 2.6k
- Avg merge
- 13h 16m
- Merged PRs (30d)
- 17
Description
The "params" add-on should be moved out of zaproxy core to allow for easier upgrades/enhancements.
https://github.com/zaproxy/zaproxy/tree/main/zap/src/main/java/org/zaproxy/zap/extension/params
The initial PR has already been opened:
Outstanding tasks:
- Have other add-ons use the new add-on.
- Deprecate/disable core functionality.
- Add the add-on to the weekly.
- Both handled in: https://github.com/zaproxy/zaproxy/pull/9339
- Migrate params DB components (from core to add-on)
- Remove params content from zap-core-help
- Handled in: https://github.com/zaproxy/zap-core-help/pull/631
- Add placeholder/redirect on the website
[!NOTE]
Currently for testing purposes it's necessary to manually disable the core extension in ZAP's options (https://www.zaproxy.org/docs/desktop/ui/dialogs/options/ext/).(I will look at only loading/enabling the new one when core functionality is deprecated/disabled, in another PR if needed depending on timing etc.)
Contributor guide
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.
Assessment
This issue has not been assessed yet.