Bannerbear Detector V2

[shahzadhaider1]

Description:

This pull request introduces a new V2 detector for Bannerbear API keys. The new version adds support for modern key formats and implements live API verification to eliminate false positives.

Implementation Details

• New V2 Detector: A new bannerbearv2 detector was created to house the updated logic.
• Precise Regex: The detector uses the pattern \b(bb_(?:pr|ma)_[a-f0-9]{30})\b to accurately identify both key formats.
• API Verification: A verification function calls the GET /v2/auth endpoint.
  • A 200 OK response validates a Project API Key.
  • A 400 Bad Request with a specific error message validates a Master API Key, in line with the official API documentation.
• Keywords: Added bannerbear, bb_pr_, and bb_ma_ to the keyword list for efficient scanning.

Testing

To ensure correctness and reliability, this change includes:

• Pattern Tests: Tests validating the regex against positive and negative samples.
• Integration Tests: Live API tests confirming the verification logic for valid Project keys and invalid keys.

Closes OSS-143

Checklist:

• Tests passing (make test-community)?
• Lint passing (make lint this requires golangci-lint)?

[kashifkhan0771]

We are using same API to verify V1 and V2 secret types. Why are we not using same function in both versions?

[shahzadhaider1]

@kashifkhan0771 The V2 verification function includes specific logic to differentiate between Project and Master API keys. Since this additional processing is not required for V1 keys (although we could still use the same function, which would make things complex), I decided against merging them to keep the V1 verifier clean and straightforward.

[amanfcp]

LGTM!