See what a VegaSec risk report looks like before sharing a token or repository.
Public, no-login examples for token launches, DeFi repositories, AI backends and thin-evidence projects. These samples sell the artifact: a clear verdict, evidence trail, source confidence and next action your team can forward.
What buyers get
Built for
Token launch teams
Built for
DeFi builders
Built for
Web3 researchers
Built for
AI/SaaS teams with public repos
Thin Liquidity Token Audit
THIN / SOLANA
An AVOID-style launch review showing fragile pool depth, concentrated control and weak source confidence before a team exposes its community.
Operator verdict
Block from promotion
Open manual review
Signal
Liquidity
94/100
Signal
Owner control
92/100
Signal
Holder concentration
88/100
- Pool depth is too thin for public promotion
- Owner and holder concentration require manual review
- Official-source confidence is weak
Pre-Launch Token Watchlist
LAUNCH / BASE
A WATCH-style launch report with usable market data, visible liquidity limits and follow-up checks before a token team shares the asset publicly.
Operator verdict
Monitor before public promotion
Schedule follow-up scan
Signal
Liquidity
48/100
Signal
Social proof
44/100
Signal
Holder concentration
41/100
- Market data is usable but not SAFE-grade
- Liquidity and holder drift need follow-up
- Clear no-advice next action for the launch team
DeFi Repository Risk Review
public-defi-protocol/core-contracts
A Repository Audit example for a public DeFi codebase with visible activity, reviewable controls and security questions a buyer can understand.
Operator verdict
Monitor before public promotion
Schedule follow-up scan
Signal
Evidence depth
48/100
Signal
Activity cadence
45/100
Signal
Issue and PR flow
44/100
- Recent maintainer activity is visible
- Documentation and license evidence are present
- Security and CI posture still need operator review
Low Evidence Repository Snapshot
thin-evidence/api-service
An UNKNOWN Repository Audit example for public projects where the available evidence is too thin to support a buyer-facing trust label.
Operator verdict
Insufficient evidence
Collect more evidence
- Public evidence is too thin
- Documentation and security files are missing
- Manual evidence collection is required
Public-data disclaimer
Example reports are product samples, not live provider output. Live Token Audit and Repository Audit routes require submitted context and fail closed to UNKNOWN when evidence is missing, private, malformed or unavailable.