ngl
IFFY

55 / 100

$BROW

0x2142…daafde· Robinhood Chain

ngl, not gonna lie

A real open-source security tool exists, but its cloud product could not be seen working.

The project has a real GitHub repo with 362 commits and a push 4 days ago, which backs its open-source engine claim. The Cloud API sits behind GitHub sign-in, so the agent never saw it work. The token contract source is unverified, and no on-chain or wallet flow ties the product to $BROW. Nothing found points to a scam.

Ask the agent

Checked 1 h ago

Red flags0

No red flags found.

Watch out5

  • Cloud API could not be tested

    GitHub sign-in needs real credentials, so the agent never got an API key. The /api page is only marketing copy, so the verify feature was never seen working.

    screenshotscreenshotclaim source
  • Token contract source is not verified

    Nobody can read what the contract does, since it is not on Sourcify. This is a risk, though not proof of wrongdoing.

    token
  • No link between the product and the token

    The site has no wallet connect or contract-address checker, so the coin has no visible use in the product.

    screenshot
  • Moderate holder concentration

    The top 10 wallets hold 49%, a count that includes pools and lockers. About 0.7% of supply is burned.

    tokenburn address, 0.694%
  • Young domain and project

    The domain was registered 4 months ago, in line with the token launch and repo history. That gives a short track record.

    registration

Checks out2

  • Real open-source code exists

    The alexverify/eyebrow repo has 362 commits, 2 contributors, 433 files in Go and TypeScript, and a push 4 days ago. This fits the claimed open-source engine.

    alexverify/eyebrowclaim source
  • X account looks organic

    0 of 200 sampled followers are empty accounts. The account has 878 followers and posts get a median of 25 likes. The CA is posted by 15 accounts, 13 of them with 1K+ followers.

    @eyebrowCC@sololevelhunter@HeroGemFinderr@neobleck

Ask the agent

Anything about $BROW. ngl answers from this check, or goes back to the site and tries what you ask.

Hands-on tests

  • Couldn’t testDashboard access and GitHub sign-in

    GitHub sign-in needs real credentials

    What it did:
    Opened Dashboard, clicked 'Sign in with GitHub', filled test@example.com and TestOnly123 on the login form and submitted (landed on /session). Retried Dashboard and sign-in several times.
    What the site showed:
    Sign-in kept returning to /login; no API key was shown. Sign-in on GitHub requires real credentials a test visitor cannot provide.
    Screenshot: GitHub sign-in needs real credentials
  • Couldn’t testVerify / API key page

    Verify tool gated behind sign-in

    What it did:
    Opened /api and read the page HTML looking for a Verify control (twice).
    What the site showed:
    The API page shows marketing copy and links ('Get a free key' to /dashboard, 'Read the API reference'); no interactive verify form was exposed to a visitor without login.
    Screenshot: Verify tool gated behind sign-in
  • Couldn’t testWallet connection and coin check for $BROW

    No wallet flow reached for $BROW

    What it did:
    Not attempted: the product requires a GitHub login with an API key, and no wallet or contract-address checker was offered on this site.
    What the site showed:
    No wallet connect or token input on eyebrow.cc pages reached.
    Screenshot: No wallet flow reached for $BROW
New checkBrowse all checks