Last updated: August 3, 2021
Read time: 2 Minutes
Before you submit your extension, you should ensure that it will have the best chance of being accepted. Read the guidelines to see what we think makes a good extension. Some of the key points are:
The extension should not duplicate the functionality of Burp Suite or existing BApps.
The extension should use Burp Suite networking.
The extension should follow coding best practices such as maintaining responsiveness and unloading cleanly.
The extension should work well with Burp Suite use cases such as offline working and large projects.
BApps are forked from the source code of the creators. If you'd like to see the source code of current BApps, you can look at it in our repository.
To submit your extension, you will need:
A link to the GitHub repository where all the relevant source code is stored.
A name and a good description of what your extension does.
A description of how your extension works, how to use it, and any setup information needed to use the extension.
Once you have all this, contact us and we will review the extension.
Once we have your extension, we will compile and review it to make sure it's suitable for the BApp store. We'll review it against the guidelines as follows:
Ensuring that the extension is not replicating any existing functionality or available extensions.
A code review, to check compliance with the guidelines.
An automated review checking for the usage of any key functions.
A virus/malware scan.
Manual testing of the extension.
We'll get back to you with any questions we might have or suggestions for improvement. Once we've reviewed the extension, we'll get back to you on whether it will be going in the BApp store.
The process for updating a BApp is as follows:
Create a pull request against PortSwigger's fork of your repository. We will only accept pull requests from the forked repository.
Email us to tell us that you've opened a pull request.
We will review the changes and merge them into the PortSwigger fork.
We will test the extension, and publish the updated version to the BApp Store.