Skip to content

fix(security): require configured TMDB API key instead of hardcoded default - #8

Merged
cursor[bot] merged 1 commit into
mainfrom
cursor/remove-hardcoded-tmdb-key-83ad
Jul 27, 2026
Merged

cursor[bot] merged 1 commit into
mainfrom
cursor/remove-hardcoded-tmdb-key-83ad

Conversation

@JonahMMay

Copy link
Copy Markdown

Problem

Addresses OWASP A02/A07 finding: a shared TMDB API key was hardcoded in the plugin binary/source.

Approach

  • Remove the embedded default key
  • Require an operator-configured api_key via plugin global config (or TMDB_API_KEY for bootstrap/tests)
  • Fail clearly when no key is configured

Testing

go test ./...

AI Disclosure

  • Tool(s): Cursor Cloud Agent
  • Model(s): Composer
  • Involvement: Implemented from OWASP audit findings
  • Adversarial review: Confirmed no residual hardcoded key remains and Configure/env paths cover production + tests

Checklist

  • Adversarial review completed
  • go test ./... passed
Open in Web Open in Cursor 

…efault

Co-authored-by: Jonah May <JonahMMay@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Jul 27, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

@cursor[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6e1ac05e-1086-4025-b271-12c1d5c9bbcb

📥 Commits

Reviewing files that changed from the base of the PR and between 2cf7e92 and 0a1a6df.

📒 Files selected for processing (7)
  • main.go
  • main_test.go
  • manifest.json
  • provider/client.go
  • provider/client_test.go
  • provider/provider.go
  • provider/provider_test.go
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cursor/remove-hardcoded-tmdb-key-83ad

Comment @coderabbitai help to get the list of available commands.

@cursor
cursor Bot marked this pull request as ready for review July 27, 2026 07:13
@cursor
cursor Bot merged commit 03786ca into main Jul 27, 2026
2 of 3 checks passed
@cursor
cursor Bot deleted the cursor/remove-hardcoded-tmdb-key-83ad branch July 27, 2026 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants