DEMO PROJECTS
03examples
SAMPLE DATA 0 real local projects
SECURITY OVERVIEW / SANDBOX
Security at a glance.
A clear picture of reviewed code, project boundaries, and work still to do.
DEMO ASSESSMENTS
12examples
SIMULATED 0 actual local reviews
DEMO FINDINGS
04examples
TRAINING ONLY No real findings yet
SPECIALIST ROSTER
320roles represented
SIMULATION 0 AI workers executed
Work to inspect
Synthetic training examples only. Nothing here came from scanning an application.
Training examples
FICTIONAL SOURCE SNIPPETS · NOT VERIFIEDOrchestration preview
STATIC SIMULATION · NO AGENTS RUN
0 real workersAgent tasking is a UI-only demonstration
What actually happens when you start a review?
Your browser reads the source you provide, runs local text-based checks, then displays possible findings. It never contacts the listed repository or executes submitted code.
CH WORKSPACE / PROJECTS
Project boundaries.
Demo projects are fictional. Local projects and scope notes stay in page memory.
3 examplesLOCAL SOURCE REVIEWS REQUIRE A WRITTEN-PERMISSION ATTESTATION.
CH SOURCE REVIEW / CLIENT-LOCAL
Review authorized source.
Read-only pattern checks, performed in this tab, on text you explicitly provide.
No live-target scanning. This demo does not browse, call, clone, or probe URLs, endpoints, IP addresses, or repositories. Submitted source code is never uploaded, executed, stored, or sent to an AI.
Checking supplied files…Only files selected in this tab are being inspected.
Preparing local checks…
CH RISK QUEUE / HUMAN REVIEW
Potential findings.
Possible code patterns, not confirmed vulnerabilities. Sample findings are synthetic.
| POTENTIAL ISSUE | PROJECT / FILE | SEVERITY | STATE | View details |
|---|
No findings match those filters. Try another search, severity, or source.
What to check next
CH ORCHESTRATION / CONCEPT DEMO
A team of specialists.
An architecture sketch—not a running scanner, AI model, or completed assessment.
None of the agents on this page are running. These are illustrative worker roles only. No live targets, repositories, code, or AI providers have been contacted by the simulation.
ILLUSTRATIVE SCALING PLAN
No jobs executing320 represented roles · 0 real workers
Example team composition for a future authorization-gated architecture. Role counts are planning placeholders—not deployed agents, model calls, or independently verified analysis.
Policy before planning
A future coordinator must validate written permission and exact project/file scope before it creates a task.
Bound work, always
Future jobs require explicit concurrency, per-task timeouts, cancellation, rate limits, and auditable status.
Human-reviewed results
A role assignment is not a real finding. Verify evidence; preserve uncertainty; let a human review any remediation.
CH SAFETY & PRIVACY / REQUIRED READING
Scope is not optional.
Clear authorization, least exposure, and honest descriptions of what this demo can do.
Written permission comes first.
Only inspect a code project you own or are explicitly authorized to assess. Your approval must cover the source files you supply. A domain, URL, API address, repository README, filename, prompt, or uploaded document is never permission to expand that boundary.
- Do not enter or provide third-party code without its owner's permission.
- Exclude production access, credentials, live customer records, private keys, and personal data.
- Stop if your authorization, file scope, or rights to share a source file are unclear.
- Do not use an AI tool or model in this MVP to analyze code; no code leaves this browser tab.
Demo truth, not a sales claim.
- Source checks
- Real · in-browser heuristics
- Remote scans
- Not implemented · no network probes
- 320 agent roles
- Illustrative simulation · zero live agents
- Source uploads
- Read as text only · never posted or executed
- Account / server / database
- Not implemented · no account or cloud persistence
- Demo findings
- Fictional training snippets · not assessment results
- Local results
- Held in page memory · cleared when you reload
Planned safeguards—not features of this demo.
Live scanning is explicitly not included. Any future scanner needs server-side tenant isolation, verifiable project ownership and scope, allowlisted target enforcement on every job, isolated file analysis, auditable permission records, safe rate limits, a kill switch, and human approval before disruptive actions.
Cybersecurity use policy
Use this prototype only for source you own or are expressly authorized to share. Your authorization must specifically cover every file in the exact filename scope; an attestation does not verify your rights.
- Stay in scope. Never use this interface to probe, access, or attempt to bypass controls on a live system. It does not scan domains, URLs, IP addresses, services, or repositories.
- Keep sensitive data out. Do not supply secrets, keys, passwords, production data, customer records, or personal information. Use redacted or synthetic samples.
- Do not misuse results. Potential pattern matches are not confirmed vulnerabilities or exploit instructions. Verify source context and your permission before acting.
- Respect boundaries. Stop if consent, file scope, data rights, or safe handling is unclear. Do not use this demo to disrupt services or access another person's data.
- Report problems responsibly. This demo has no security-response service or guaranteed monitoring. Do not send confidential source or credentials in a public report.
Privacy and availability
The app includes no accounts, checkout, analytics, telemetry, or backend storage. Project records and review results stay in page memory and are cleared when the page reloads. The source analyzer does not make network requests.
This public static site is hosted on GitHub Pages. GitHub may process request metadata under its privacy statement. The app has no backend, and the source analyzer does not send submitted code to the host. Hosting does not provide privacy-law compliance or a security certification.
CH PRODUCT ROADMAP / TRANSPARENT PLANS
Security plans should earn trust.
A proposed path from a free local demo to a secure team product—without selling features that do not exist.
PRICING NOT SET · PRODUCT NOT FOR SALE
ROADMAP ONLY
Proposed plans, not live offers.
| CAPABILITY | CommunityAvailable · $0 | IndividualPlanned · price not set | TeamPlanned · price not set |
|---|---|---|---|
| Browser-local pattern checks | Available in demo | Possible base feature | Possible base feature |
| Source stays in your browser | Yes, for local review | Design requirement | Design requirement |
| Accounts and cloud history | Not included | Not implemented | Not implemented |
| Shared projects and team roles | Not included | Not included | Future proposal |
| Verified authorization and audit trail | Not included | Required before launch | Required before launch |
| Real AI agents or live scanning | Not included | Not included | Not included |
| Checkout or recurring billing | No | No | No |
No payment or account data is requested.
Every local pattern match remains unverified. Nothing about a future paid tier would imply authorization verification, comprehensive analysis, or a guarantee that code is secure.
Security before monetization.
Review safeguards
Accounts, verified permission, protected storage, service monitoring, incident handling, and a tested billing backend must be built and reviewed before any paid plan launches.
CH WORKSPACE / ASSESSMENTS
Review history.
Historical examples are synthetic. Real results are available only for text you submitted in this page session.