Bitbucket Integration
Scan enabled Bitbucket Cloud repositories across reachable branch changes, with progress and skip checks.
Key Features
- Bitbucket Cloud OAuth and access-token connection paths
- Repositories discovered within a selected workspace
- Enabled branch targets scanned across scheduled jobs
- Completed work and access failures checked per target
Requirements
- 1A Bitbucket Cloud identity or token with access to the intended workspace and repositories
- 2A Cremit account allowed to manage scan sources
- 3At least one repository target selected for scanning
Step-by-step setup guide
Review the steps needed to configure this integration.
What does the connection cover?
Cremit discovers repositories visible through the selected Bitbucket Cloud workspace connection and creates separate scan targets. Enable the repositories you want checked. A workspace connection does not prove that every repository is accessible or that a newly discovered repository has completed a scan. Bitbucket Data Center and Server are outside this connection.
The worker examines supported changes in repository branches. Normal clone scanning has a per-job file budget; API fallback has smaller commit and file budgets. A very large repository can be limited to the default branch in a job, and unfinished work can continue later. Check target enablement, branch progress, completed jobs and skipped or failed content before claiming full history was covered.
Connect and select targets
In Cremit Platform, open Configuration → Scan Sources and add Bitbucket. The current form offers an OAuth connection and an access-token path. With OAuth, authorize Bitbucket and select or enter the workspace. With an access token, use a token with the required repository access and enter the workspace identifier. Review the repositories returned by discovery, then enable the ones you intend to scan.
If a repository is missing, check the account or token scope and workspace identifier, then refresh discovery. If it appears but has no completed scan, inspect its target and job status. Do not infer coverage from a workspace name alone.
Verify and respond
Commit a harmless, nonworking example string to a repository and branch you control. After the relevant scan finishes, check the finding location and branch status. Never expose a working key to test the connection. A committed secret can remain in Git history even after its latest-file copy is removed; whether that credential still works requires a supported issuer check or manual verification.
For a confirmed exposed key, identify the service owner and rotate or revoke it at the issuer. Removing the line from a repository does not invalidate the key.
Primary documentation
Other integrations in this category
GitHub
Scan enabled repositories available to the GitHub connection; review separate PR, conversation and GHCR coverage.
Learn moreGitLab
Scan enabled GitLab repository targets for credentials in reachable branch history, subject to job and access limits.
Learn moreAWS S3
Find credential patterns in supported, readable objects from connected S3 buckets.
Learn more
Get started now
Review the setup steps and required permissions for the Bitbucket integration.