SpecOps, OpenAPI/Swagger Workbench

[Hannah-PortSwigger]

Extension URL

https://github.com/rawatprince/SpecOps

Author name

Prince Rawat

Template identifier

• template:03-create-parent-for-update

[Hannah-PortSwigger]

The extension's name should be descriptive of the functionality it provides. Feedback has been provided via email.

To reopen this issue, please tag me directly and I'll make sure it ends up where it needs to go 😊
The typical mechanism for reopening an issue would be to post a comment with /reopen.

[rawatprince]

/reopen @Hannah-PortSwigger - Thank you for reviewing my extension and providing valuable feedback.

I named the extension SpecOps because it automates the process of importing, parsing, and interacting with API specifications, giving users control over endpoints, parameters, authentication, and attacks, all directly from the specification.

Spec → Refers to the API specification (OpenAPI/Swagger).
Ops → Refers to the operational testing capabilities such as endpoint discovery, bulk ping, parameter injection, and Burp integration.

If permitted, I'd prefer to retain SpecOps, as it has already become part of the tool's identity and aligns with Burp's community tone, short, memorable, and tech-savvy. To ensure clarity for new users, I can update the listing title and description to read:

SpecOps: OpenAPI/Swagger Workbench for Burp Suite

That said, I completely understand your guidelines around descriptive naming.

As an alternative, I'd also be comfortable renaming the extension to OpenAPI Workbench, which emphasizes that the tool creates a complete testing workbench for OpenAPI-defined APIs.

Please let me know which option works best for your submission process. I can update the repository and metadata right away.

[github-actions]

⚠️ Only the original issue creator can reopen this issue using the /reopen command. Please ask a maintainer for assistance or create a new issue if needed.

[Hannah-PortSwigger]

Hi @rawatprince

Thank you for your quick response!
We could do a longer title, like your repository suggestion - "SpecOps, OpenAPI/Swagger Workbench"? That should then be the best of both worlds.

Please let me know if you would be ok with that 😊

[rawatprince]

@Hannah-PortSwigger Perfect, that works for me! Let's go ahead with SpecOps, OpenAPI/Swagger Workbench as the final title.

Thanks again for helping balance both clarity and identity. Really appreciate the quick turnaround.

[rawatprince]

/reopen @Hannah-PortSwigger - If you need any additional details, documentation updates, or minor code adjustments before the code review stage, please let me know, i'll be happy to make them right away.

[rawatprince]

/reopen - @Hannah-PortSwigger - please let me know if any other details are required.

[github-actions]

⚠️ Only the original issue creator can reopen this issue using the /reopen command. Please ask a maintainer for assistance or create a new issue if needed.