FlawRook
Sign in Join the beta
Early access · Powered by Binerals

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.

No code access needed to start: just send us your lockfile.
Binerals / Core Platform
live watch
log4j-core 2.14.1
Maven · production
CVE-2021-44228 · exploited
lodahs
npm · any version
malicious package
nginx
infrastructure · watching since 1 Jan 2026
18 new · to review
Django 3.2
PyPI · production
66 advisories
left-pad 1.3.0
npm · production
no known advisories
OSV · GHSA · NVD · CISA KEV
synced 09:00_
Public advisory data for 8 package ecosystems and 57 infrastructure products, plus code checks in your pipeline.
OSV.dev◆GitHub Advisory Database◆NVD◆CISA KEV◆npmPyPIMavenGoRubyGemscrates.ioNuGetPackagist◆nginxPostgreSQLRedisKubernetes◆secretscode patternsGitHubGitLabBitbucket◆ OSV.dev◆GitHub Advisory Database◆NVD◆CISA KEV◆npmPyPIMavenGoRubyGemscrates.ioNuGetPackagist◆nginxPostgreSQLRedisKubernetes◆secretscode patternsGitHubGitLabBitbucket◆
How it works

Two ways in. Then it keeps watch on its own.

No-code mode

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.

Ready in minutes · nothing to install
Full mode

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.

Code stays on your runners · only findings come back
01

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.

02

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.

03

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.

Stack watch

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.

Exploited first

Anything in the CISA catalog of actively exploited vulnerabilities goes to the top, with the date it was listed and known ransomware use.

Watch without a version

Not sure which nginx build runs where? Watch the product and get every advisory published after your start date, marked for review.

Lockfiles and SBOMs

Bring the lockfile or SBOM your build already produces, from the package managers teams use most. Upload again and only what changed moves; triage on everything else stays put.

Infrastructure too

57 products mapped to NVD, from nginx and PostgreSQL to Redis and Kubernetes, matched by version range.

Code scanning

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.

Secrets, in code and history

API keys, tokens and passwords caught in the change and in the git history, with values masked in every report.

Risky code patterns

Injection, unsafe HTML, weak crypto and other patterns that turn into incidents, flagged on the exact line.

A gate that blocks only what is new

Only issues a merge request introduces can block it. What already sits on main goes to the backlog instead of stopping the team.

Signal, not noise

Security rules only, test and docs folders left out, and the same issue in many files reported once.

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

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.
Delivered to your channels
Email Slack Discord
Pick the channel per alert type: urgent alerts to an incident channel, the daily digest to email.
Urgent · actively exploited · production
CVE-2021-44228 is exploitable in Core Platform production
Component
log4j-core 2.14.1
Severity
Critical · CVSS 10.0
Exploited
In CISA KEV since 10 Dec 2021 · ransomware use
Fix
Upgrade to 2.15.0 or later
Open the finding Assign an owner
Roadmap

One fortress, built in stages.

In beta

Stack watch and alerts

Packages and products watched against public advisories, urgent alerts and a daily digest.

In beta

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.

Next

Leaked company accounts

Monitoring of leaked credentials for your company domain, from darknet sources.

Beta test

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
Interested in
We use these details only to contact you about the beta. Privacy policy

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.