Security evidence for AI-built software
The scanner is free. The proof is the product.
Verglos scans AI-assisted JavaScript and TypeScript repos for the security mistakes agents keep writing, then turns the result into evidence a founder, agency, or engineering team can actually use.
$ npx verglos
scanned 1,247 files in 42s
report: verglos-report.html + verglos-report.json
critical / D4-004
credential-shaped value in source
high / AI-005
unresolved package name in lockfile
fix
move to env, rotate, pin dependency
Critical risk
1.6.0
npm release
published package, local CLI, Node 20+
10
risk domains
secrets, deps, injection, auth, data, runtime
300
repo campaign
ICP scan campaign used to shape the product
0
source upload
V1 scanner writes reports on your machine
10-domain scanner
Built from the bugs AI agents make cheap to create.
The domain model stays explicit: injection, auth, access control, cryptography, misconfiguration, supply chain, API surface, data exposure, runtime, and monitoring.
Domain 01 of 10
Injection & input flaws
Critical
Every piece of user input is a weapon if it reaches a dangerous sink unsanitised. We trace source-to-sink across your codebase — SQL, NoSQL, command exec, XSS, SSTI, path traversal — and flag the concatenations, spreads, and eval calls that turn a request into a takeover.
sample finding
element.innerHTML = req.query.name
app/user/[id]/page.tsx:42
Domain 01 of 10
Injection & input flaws
Every piece of user input is a weapon if it reaches a dangerous sink unsanitised. We trace source-to-sink across your codebase — SQL, NoSQL, command exec, XSS, SSTI, path traversal — and flag the concatenations, spreads, and eval calls that turn a request into a takeover.
What Verglos catches
- SQL / NoSQL
- Command exec
- XSS (stored / reflected / DOM)
- SSTI
- Path traversal
- XXE
Sample finding
⚠ CriticalDomain 01
element.innerHTML = req.query.name
→ app/user/[id]/page.tsx:42
Evidence path
Enterprise thinking without pretending to be enterprise theater.
Verglos is designed to move from local findings to durable proof: CI enforcement, monitoring, signed attestations, verification URLs, SBOMs, and client-ready reports.
01
Scan before handoff
Run the CLI locally and get findings, paths, snippets, fixes, score, and AI-risk signal before handoff or diligence.
02
Separate alerts from evidence
The report is designed to be read by builders first, then turned into proof for clients, procurement, or internal security review.
03
Graduate into continuity
Pro and Studio move beyond one-off scans: CI thresholds, monitoring, activation, attestations, verify URLs, and white-label reports.
Why it matters
The invisible cost you're paying today.
Not the bugs Verglos finds — the ones you don't. Every AI-assisted stack carries a handful of buried failure modes that won't announce themselves. Here's what changes when you can see them.
$29/mo · less than one hour of dev time
The developer
You stop needing to remember.
The scan you meant to run last Tuesday is the one that would have caught the CVE that shipped today. Verglos watches your dependency tree hourly and emails the moment a critical is published. No calendar reminder, no manual re-scan, no discipline debt.
The agency
Client handover without the awkward Zoom.
Every AI-built app you ship carries the same buried defaults — wildcard CORS with credentials, jwt.verify accepting alg=none, MD5 password hashes. Your client's security review will find them. Better they surface at build time on your machine than in a pen-test report three months in.
The founder
The 3am email you don't want but need.
Log4j, event-stream, whatever ships next — critical CVEs land at 2am UTC on a Sunday and your customer notices before you do. Verglos flips that: an email arrives within the hour of publication, deduped so you get it once, delivered through email, Slack, or webhook. Cheaper than one bad Monday.
The agent user
AI can't ship the same bug twice.
Your coding agent will write Math.random() for a session token because a tutorial did. It'll suggest a package name because it hallucinated one. Verglos plugs into Cursor, Claude Code, Windsurf, and Cline as an MCP tool — the agent asks Verglos before writing risky code or installing a suspect package. Correction happens inside the flow, not after the merge.
Language coverage
JavaScript and TypeScript first.
JS/TS is live today because that is where Verglos has real detector coverage, package analysis, and provenance signal. Other stacks stay on the request list until they are actually supported.
Live now
JavaScript and TypeScript first.
JS
TSCovers Node.js, Next.js, React, Express, Fastify, and npm workspaces.
Available today
LiveJavaScriptTypeScriptCovers Node.js, Next.js, React, Express, Fastify, and any npm / pnpm / yarn workspace. Ten detection domains — secrets, injection, dependency CVEs, misconfigurations, git history, and more.
Requested next
Coming
Python
Go
Ruby
Java
PHP
Rust
C# / .NET
Swift
KotlinWant your stack prioritised? Tell us which one you ship on →
npm
Install in one command.
The package is the fastest path to value: no signup, no install ceremony, no source upload.
GitHub
Inspect the scanner.
Technical reviewers can inspect the CLI, detectors, packages, docs, release notes, and evidence docs.
Top Notchh
Backed by a product company.
Verglos is part of a focused product portfolio, not a one-off landing page or loose security script.
Plans
Free is the complete local scanner.
Run it as many times as you want locally. Paid tiers are for teams that need enforcement, monitoring, evidence, handoff, and readiness workflows around the scan.
Free plan
Unlimited local scans. Full findings. Full paths. Local HTML and JSON reports. No account required.
Live
Free
$0
For: Developers, founders, agencies
Use: Unlimited local repo checks.
Unlimited local scans. No account, no source upload, no paywall for paths or line numbers.
- /Full 10-domain static scan
- /Security score /100
- /All file paths + line numbers
- /Secret detection, entropy, git-history scan
- /Dependency CVE audit via OSV
- /AI-authored code detection
- /Slopsquat / hallucinated-package check
- /Local HTML + JSON report
- /Pre-commit hook
- /MCP server
- /CI blocks on criticals
- /Unlimited local use
Live
Pro
$29/mo
For: Serious solo devs and small teams
Use: CI discipline and ongoing dependency risk.
For teams that want the scanner to keep enforcing standards after the first local report.
- /Everything in Free
- /CI score thresholds
- /Continuous CVE monitoring (hourly)
- /Email / Slack / webhook alerts
- /Agent-surface rule pack (MCP configs)
- /API-hardening rule pack
- /Deep-auth rule pack (JWT / cookies / hashes)
- /verglos fix — framework-aware headers
- /30-day score-history dashboard
- /Offline-safe license (Ed25519 signed)
Validation
Studio
$199/mo
For: Agency owners and delivery leads
Use: Client handoff, liability, and proof of AI-built work.
Agencies do not need another noisy scanner. They need client-ready evidence that helps a project pass handoff.
- /Everything in Pro
- /Signed attestations
- /Public verify URLs
- /White-label client reports
- /SBOM export
- /License-risk flagging
- /verglos rotate
- /Rotation runbooks
- /1-year evidence history
- /Client-facing share links
Planned
Compliance
$499/mo
For: Founders and heads of engineering
Use: Procurement, SOC 2 readiness, diligence.
For teams preparing security answers before an auditor, customer, or enterprise review forces the conversation.
- /Everything in Studio
- /SOC 2 readiness assessment
- /GDPR data-map report
- /Security posture PDF
- /Evidence archive
- /Audit trail
- /Metered AI triage
- /Threat-intel feed
- /Priority support
- /3-year evidence history
| Capability | Free | Pro | Studio | Compliance |
|---|---|---|---|---|
| Full 10-domain static scan | Yes | Yes | Yes | Yes |
| All file paths and line numbers | Yes | Yes | Yes | Yes |
| Local HTML + JSON report | Yes | Yes | Yes | Yes |
| AI-authored code detection | Yes | Yes | Yes | Yes |
| Slopsquat / hallucinated package check | Yes | Yes | Yes | Yes |
| MCP server | Yes | Yes | Yes | Yes |
| CI score thresholds | Criticals only | Yes | Yes | Yes |
| Continuous CVE monitoring + hourly alerts | No | Yes | Yes | Yes |
| Email / Slack / webhook alerts | No | Yes | Yes | Yes |
| Agent-surface rule pack (Cursor / Claude Code / Windsurf / Cline) | No | Yes | Yes | Yes |
| API-hardening rule pack (rate limit, body size, CORS+creds) | No | Yes | Yes | Yes |
| Deep-auth rule pack (JWT / cookies / password compare / weak hashes) | No | Yes | Yes | Yes |
| Score-history dashboard | No | 30 days | 365 days | 3 years |
| verglos fix (framework-aware headers) | No | Yes | Yes | Yes |
| Signed attestations | No | No | Planned | Planned |
| Public verify URL | No | No | Planned | Planned |
| White-label reports | No | No | Planned | Planned |
| SBOM + license risk | No | No | Planned | Planned |
| SOC 2 readiness output | No | No | No | Planned |
Top Notchh operating stamp
Built by a product company, not a scanner content farm.
Top Notchh Solutions builds practical software products from real operational pain. Verglos is the security-evidence product in that portfolio: specific, local-first, honest about maturity, and built to become infrastructure for AI-assisted delivery.
From the Journal
Research and product notes.
Original research from the Verglos scan campaign, positioning notes, and product decisions — published on the Top Notchh Journal.
Read the full Journal →Research · scan campaign
2026-07-30
We scanned 300 world-class TypeScript & JavaScript repos. 57.7% had critical or high findings.
Verglos ran the ICP-relevant top 300 GitHub repositories. 169 of 293 successful scans surfaced critical or high risk — the finding that shaped the product.
Read on Top Notchh →Patterns · developer
2026-07-30
The security bugs AI code keeps writing: 8 patterns from the ICP top 300.
SQL injection, weak tokens, IDOR, wildcard CORS, verbose stack leaks, hard-coded secrets, mass assignment, and slopsquat risk — the AI-era patterns that repeat across the campaign.
Read on Top Notchh →Positioning · comparison
2026-07-25
Verglos vs Snyk, GitHub, Semgrep, Socket, and Gitleaks: why AI-built software needs a different layer.
A founder-friendly comparison against the top scanners and why AI-built software needs evidence, not more alerts.
Read on Top Notchh →Thesis · agencies & founders
2026-07-24
The security evidence layer for AI-built software.
AI-assisted teams do not just need scanners. They need evidence they can show clients, buyers, and auditors. The business case for Verglos.
Read on Top Notchh →Disclosure · secrets
2026-07-19
How Verglos handles active credential disclosures.
A responsible-disclosure note on live credentials, private maintainer contact, and why public proof should wait until rotation is confirmed.
Read on Top Notchh →
FAQ
Boundaries make the product stronger.
Is Verglos just another scanner?+
No. The scanner is the entry point. Verglos is built around evidence: AI-code risk signal, report artifacts, MCP guardrails, CI enforcement, and client-ready proof.
Does Verglos upload source code?+
The V1 scan runs locally and writes local HTML and JSON reports. Networked flows are explicit: login, activation, monitoring registration, and future hosted evidence.
Which languages are supported today?+
JavaScript and TypeScript are live. Other language icons are request-list indicators, not shipped coverage.
Who is behind Verglos?+
Verglos is built by Top Notchh Solutions, an AI-native product company building practical software products from real operational problems.