Submit source
Connect GitHub, choose a repository, and confirm the branch or source snapshot that V2P should assess.
From source snapshot to verifiable result.
V2P gives your team one understandable path from submitted code to evidence, remediation, re-audit, and—only when you choose—a scoped public result.
One controlled evidence loop
Your source snapshotThe selected repository state and declared audit scope.
Static scanners + AI specialistsThe evidence maps into 4 pillars and 20 weighted checks.
Private evidence and next actionsReview findings before deciding what to fix or publish.
GitHub repository importFile-level source evidenceCoverage and status gatesFresh re-audits after changes
The complete program, step by step.
Each stage answers a different question, so your team always knows what is happening and what decision comes next.
Scan with two analysis layers
Deterministic, non-AI static scanners check known patterns while AI specialist agents review relevant source across the four pillars.
Review evidence
Open the private report to see category scores, file paths, severity, source excerpts, context, and suggested next actions.
Repair and re-audit
Apply changes under your own review process, then run a fresh audit against the updated source snapshot.
Publish the result
When eligible and ready, issue a certificate and seal that link to a scoped verification record.
Know what goes in—and what comes back.
V2P evaluates submitted source. It does not silently change your repository, deploy code, or turn private findings into public claims.
What you provide
The source and scope you want assessed.
- A GitHub repository and selected branch or source snapshot
- The scope you want assessed and any areas intentionally excluded
- Enough eligible source for the audit coverage gates to be meaningful
- A deliberate decision about when an updated snapshot is ready to re-audit
What V2P returns
Evidence you can review and use.
- Twenty weighted category scores and four pillar rollups
- Private findings with severity, file references, evidence, and context
- Reviewable remediation guidance, prompts, and suggested patches
- Coverage details, public-status gates, an overall score, and the next decision to make
You control the boundary.
Detailed findings remain private. A public verification record is created only when an eligible result is issued.
Private by default
Source files, proprietary logic, detailed findings, excerpts, remediation notes, and internal workflow stay inside the authenticated product.
Scoped when published
An issued result can show the score, public status, declared scope, issue date, audit version, and source fingerprint—without publishing the source itself.
Start with one source snapshot.
Connect a repository, see the evidence, and decide the next step with the complete 4-pillar, 20-point methodology.
