Find the flaws before attackers do.
FlawRook watches every package and product you run for new vulnerabilities, and scans your code on every merge request for leaked secrets, vulnerable dependencies and risky patterns. You hear about it when it matters, not all day.
Two ways in. Then it keeps watch on its own.
Just send us your lockfile.
Upload the lockfile or SBOM your build already produces, and add infrastructure like nginx or PostgreSQL by name. FlawRook never sees your code and needs no access to your repositories or servers.
Connect your repository.
Add one step to your GitHub, GitLab or Bitbucket pipeline. Lockfiles are picked up on every push, and each merge request is scanned for secrets and risky code, with a pass or block right in review.
Tell us what you run
Send a lockfile or an SBOM and add products by hand, or connect a repository so lockfiles and merge requests come in on their own.
We watch and scan
Your stack is checked on a schedule against local copies of the advisory databases. Every merge request is scanned in your CI for secrets, vulnerable dependencies and risky code.
You hear first
An urgent alert when an exploited or critical vulnerability reaches production, a pass or block on every merge request, and one short daily digest.
Your stack, watched around the clock.
New advisories land every day. FlawRook matches them against what you actually run and tells you which ones reach you.
Every merge request, checked before it lands.
FlawRook adds one step to your pipeline. It scans what the merge request changes and answers pass or block, right where the team reviews code.
Also in every plan
Typos and malware stopped at the door
Names are checked against the registries as you add them. A lookalike gets “Did you mean lodash?”, a known malicious package is flagged critical.
Domain hygiene
Passive checks of your company domain: SPF, DMARC, MTA-STS, CAA, DNSSEC, TLS versions, certificates and security headers.
Your code stays on your runners
Code scanning runs inside your own CI, and only findings come back. Stack scans run on local copies of the databases.
Teams and roles
Admins, maintainers and viewers per company. Sign in with a one-time link by email, so there are no passwords to leak.
Alerts you can act on in one read.
Each alert says what is affected, where it runs, whether it is being exploited and which version fixes it, and it lands where your team already works. No dashboard to dig through first.
- Urgent alerts only for production, and only when it is exploited or critical.
- One daily digest instead of a stream of notifications.
- Every finding alerts once, never twice.
One fortress, built in stages.
Stack watch and alerts
Packages and products watched against public advisories, urgent alerts and a daily digest.
Code scanning and a CI gate
Secrets, dependencies and risky code checked on every merge request, with a pass or block back to your CI.
Leaked company accounts
Monitoring of leaked credentials for your company domain, from darknet sources.
Join the beta test.
We are bringing teams in, a few at a time. Tell us about your stack and your code, and we will write to you when a slot opens.
- Early access to FlawRook
- Onboarding with the people who build it
- A say in what ships next
We will write to when a beta slot opens.
Product updates, about once a month.
What shipped, what is next, and the vulnerabilities worth knowing about. Unsubscribe in one click.
Questions
What do I need to start?
For no-code mode, just your lockfile or SBOM, or a list of what you run. For code scanning as well, a repository and a CI pipeline where we add one step.
Do you need access to our code?
Not in no-code mode: you just send us your lockfile, and package and product names and versions are all FlawRook uses. If you also want code scanning, it runs as a step inside your own CI pipeline, so the code stays on your runners and only findings are sent to FlawRook.
Which Git hosts and CI systems work?
GitHub, GitLab, including self-hosted, and Bitbucket. Tell us yours in the beta form.
Where does the vulnerability data come from?
OSV.dev, the GitHub Advisory Database, the National Vulnerability Database from NIST, and the CISA catalog of known exploited vulnerabilities.
When can we start?
We are bringing teams into the beta a few at a time. Join the list and we will write to you as soon as a slot opens.
Who is behind FlawRook?
FlawRook is built and powered by Binerals.
Where do alerts go?
Email, Slack or Discord. Choose a channel per alert type, for example urgent alerts to an incident channel and the daily digest to email.