Frequently asked questions
In this section
- What file types are scanned?
- Can I customize what secrets are detected by the CLI tool?
- Can I find secrets before they are committed?
- Do I need a credit card to sign up?
- Do I need a GitHub account to try BluBracket?
- Does BluBracket scan new commits to repositories?
- Does BluBracket store/modify my code or any part of my code?
- How do I add a repo to monitor?
- How do I sign in to BluBracket?
- How does BluBracket code vulnerability scanning compare to Semgrep?
- How does BluBracket use my data?
- How does the BluBracket checks app check my pull requests?
- How long does it take for BB to scan new commits?
- If I create a free account via GitHub, can I check code on GitLab or Bitbucket servers?
- What can I do with BluBracket APIs?
- What can I do with BluBracket Community Edition?
- What does the BluBracket CLI tool do?
- What GitHub permissions does the BluBracket app require?
- What IDEs are supported by the CLI tool?
- What if I need more time for my free trial?
- What non-inclusive language does the BluBracket search for?
- What platforms are supported by the BluBracket CLI tool?
- What repositories can I monitor?
- What risks can the code vulnerabilty checks uncover?
- What types of secrets does BluBracket search for?
- Why is my .env file blocked?
- Why should I use the BluBracket to discover secrets in code when there are so many other tools available?