Public demonstration
Try DDC on a public repository.
Give DDC a public GitHub repository URL and, optionally, the branch, tag, or commit you want tested. The demo resolves an exact commit, performs bounded read-only static analysis, and returns a reduced result you can also download as a review PDF.
What can I test?
Use the demo to challenge a public software target before execution.
The public Try DDC page accepts a public GitHub URL plus an optional branch, tag, or commit. It does not accept uploaded files or private credentials. File-based and non-public evidence belongs in a scoped DDCAL service after the evidence-transfer boundary is agreed.
Repository risk signals
Look for suspicious paths, secret-like material, dangerous execution constructs, dependency and advisory signals, symlinks, submodules, container/CI issues, and other pre-execution concerns.
Trust and transition signals
Inspect authority, provenance, verification, transition, recovery, and resource-boundary signals rather than treating “the code runs” as proof that the system should be trusted.
Bind the evidence
Test the default branch or name a specific branch, tag, or commit. DDC resolves the target to an exact commit SHA so the released result refers to a defined software state.
Good demo questions: “Does this repository expose obvious pre-execution risk?”, “Are there authority or provenance gaps?”, “Does the CI/container boundary look unsafe?”, “Are dependencies pinned and supported by available advisory evidence?”, or “What should I review before I run this code?”
Prefer not to submit a repository to a website? Use the public Try DDC GitHub repository. You can inspect the analyzer, pin it to an exact commit, and run it in your own GitHub Actions environment so the target source stays on your runner.
DDC Demo Result
Repository preflight
Representative findings
DDC assurance signals
Need more than the demo?
Move from a public preflight to a defined assurance service.
The public demo is intentionally narrow. DDCAL services can work from public URLs, actual supporting files, or both, depending on the purchased or agreed scope. Sensitive or non-public evidence is transferred only after scope is confirmed.
DDC Snapshot
One public repository or eligible public software target. Read-only/static preflight, material assurance observations, and concise next steps.
C$69 · Focused reviewQuick Assurance Review
One defined repository, AI agent, extension, or small application. Can include a small non-confidential evidence set such as requirements, configuration, logs, traces, screenshots, or test output.
C$249 · Pre-launchPre-Launch Assurance
A deeper bounded review of architecture, authority boundaries, findings, remediation, and one post-fix verification cycle for a defined release or material transition.