ngl
IFFY

55 / 100

± 0 since last

$BROW

0x2142…daafde· Robinhood ChainAll 2 checks

ngl, not gonna lie

A real open-source security repo exists, but its main features and token link could not be tested.

The project has an active public GitHub repo with 362 commits, and its X account looks organic. The browser agent could not get past GitHub sign-in, so the Cloud API, scan console and live feed were never seen working. The token contract is unverified and nothing shows how $BROW ties to the product.

Ask the agent Watch

Checked 2 h ago

Since the last check

The last check, 3 days ago: IFFY 55. This one: IFFY 55. See that check

The project looks the same as last time. These numbers moved:

MeasuredThenNow
Market cap$176.2k$188.1k
Top 10 holders49.4 %48.2 %

Red flags0

No red flags found.

Watch out4

  • Main product was not reached

    The agent got from Dashboard to a GitHub sign-in but could not log in with dummy credentials. No API key, scan result or wallet request was seen, so the product is unproven rather than broken.

    screenshotscreenshot
  • Most site and X claims untested

    The Cloud API, hash-based change detection, runtime shim, live feed and scan console could not be checked. Only the open-source engine claim is backed.

    screenshotalexverify/eyebrow
  • Token contract source is not verified

    The contract is not on Sourcify, so nobody can read what it does. This is a risk for holders, though not proof of a trap.

    token
  • Holder concentration is moderate

    The top 10 wallets hold 48%, including pools and lockers. The wallets could not be listed, and 0.694% of supply is burned.

    tokenburn address, 0.694%

Checks out2

  • Real open-source code with steady activity

    The alexverify/eyebrow repo has 362 commits, 2 contributors and 433 files, with a push 7 days ago. This matches the claimed open-source engine.

    alexverify/eyebrowclaim source
  • X account looks organic

    883 followers with 0 of 200 sampled being empty accounts, and about 26 likes per post. The account is paid verified and about 4 months old.

    @eyebrowCC@eyebrowCC@eyebrowCC@eyebrowCC

How ngl got here

What the call rests on

  • Product · Does it exist and work?

    A real open-source repo exists, but the agent never saw the API or scan features work.

  • Claims · Are its claims backed?

    The open-source claim is backed; the rest are untested.

  • On chain · Holders, bundles, the dev wallet

    Concentration is moderate, but the contract is unverified and the top wallets could not be listed.

  • Team · X account, dev history, ngl’s memory

    There is a real GitHub and X presence with no known rug ties, but no named team.

Cross-checked

A second agent read the same evidence and tried to prove this call wrong. It found nothing to object to.

ngl has seen this before

ngl has checked 192 coins. None of them shares this coin’s dev wallet, the wallet that funded it, its website, X account, Telegram or logo.

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

  • WorksLaunching the app (Dashboard)

    Dashboard leads to GitHub sign-in

    What it did:
    Clicked 'Dashboard' on eyebrow.cc
    What the site showed:
    Navigated to /dashboard, which led to a 'Sign in with GitHub' option
    Screenshot: Dashboard leads to GitHub sign-in
  • Couldn’t testGitHub sign-in with dummy credentials

    GitHub login needs real credentials

    What it did:
    Filled username test@example.com and password TestOnly123! on the GitHub sign-in page, submitted with the Sign in button and Enter several times
    What the site showed:
    'Incorrect username or password.' alert on the GitHub login page; the password field was left empty on the last attempt, so the form asked for it again
    Screenshot: GitHub login needs real credentials
  • Couldn’t testSign in with a passkey / Google / Apple

    Passkey and social logins not completed

    What it did:
    Clicked 'Sign in with a passkey' at the start of the flow
    What the site showed:
    Passkey option was offered on the GitHub page; no result was reached from it that led to the eyebrow app
    Screenshot: Passkey and social logins not completed
  • Couldn’t testWallet connection and $BROW checker result

    Main product result not reached

    What it did:
    Not reached: the main flow stopped at the GitHub sign-in that eyebrow uses for its API key
    What the site showed:
    No wallet request, no BROW chart or result shown
    Screenshot: Main product result not reached
New checkBrowse all checks