Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create ChatGPT_API_Predictor.bambda #54

Closed
wants to merge 4 commits into from

Conversation

BugBountyzip
Copy link
Contributor

@BugBountyzip BugBountyzip commented Jan 17, 2024

Create ChatGPT_API_Predictor.bambda

Bambda Contributions

  • Bambda has a valid header, featuring an @author annotation and suitable description
  • Bambda compiles and executes as expected
  • Only .bambda files have been added or modified (README.md files are automatically updated / generated after PR merge)

Create ChatGPT_API_Predictor.bambda
One suggestion, you can replace the regexes with requestResponse.request().path() or requestResponse.request().pathWithoutQuery() for a slight speed boost
@PortSwiggerWiener
Copy link
Collaborator

Thanks for your submission and the interesting use case for bambdas and AI!

Unfortunately we don't feel that this is a good candidate for the bambda repo.
If you want this code to be reusable by a wider audience, it would be better suited to a BApp.

Using a BApp would allow you to:

  • Add a UI so that people could configure the auth token and file paths (or even render the output in the UI)
  • Use Burp's network stack rather than fork out to curl (which bypasses logging, proxy settings and can get anti-virus excited)
  • Use a context menu rather than notes to select relevant requests
  • Add robust error handling (currently any stack traces will be ignored)
  • Improve the performance as you would not need to open and close the file for every proxy item.

You can find some example BApps here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants