About / Evidence and support
Choose a project by its documented job and evidence.
TitanCSA maintains Windows applications and developer SDKs. This portal helps you find the matching source, release and first-run guide.
The catalogue covers public projects and SDK source repositories from the TitanCSA and titanfyre accounts. It does not publish private implementations or count package mirrors and account forks as separate finished products. A repository's own current README, release and licence remain the reference.
Evidence levels
| Evidence | Read it as |
|---|---|
| Source available | Code that can be inspected, with file-level licence terms |
| Offline validation passed | A checked model, descriptor or local logic path; not proof of live hardware operation |
| Signed binary | A signature result for that binary; not WHQL certification, HVCI qualification or a guarantee of no defects |
| Measured behavior | The exact version, profile, receiver and environment recorded in the result |
| Source preview | An implementation with documented live paths or distribution prerequisites still unqualified |
The benchmark lab publishes real virtual-device measurements, raw files and invalid runs. It is operated by the publisher, not an independent certification body. Its Vdevice WDF teardown finding remains open.
Licences and product prerequisites
Application/SDK source, prebuilt drivers, evaluation-source code, dependencies and OEM redistribution can have different terms. An MIT user-mode client is not an unrestricted driver licence. Some tools are complete MIT utilities with no paid unlock; others depend on separate evaluation drivers. Check the selected product instead of applying one licence assumption to the entire catalogue.
The SDK catalogue lists exact package names and install commands. A client package normally does not install a driver or its product application.
Support and contributions
Open an issue in the affected repository with its exact version, Windows build/architecture, minimal steps, expected behavior and observed result. State whether the test was offline, virtual or physical. Remove credentials, licence keys and personal information before sharing diagnostics; full kernel dumps should not be attached publicly.
The accounts publish shared support, contribution and security-reporting guidance. Repository-specific policies take precedence. Private vulnerability reporting is available on the catalogue's checked repositories through GitHub's Security/Advisories interface.
For full-driver, OEM or redistribution questions, the documented Discord username is titancsa. Availability and terms are project-specific. No support response time or certification is implied by this portal.
Authorship and this site
TitanCSA uses AI assistance for development, documentation and verification. Evidence, source attribution and current limitations take precedence over promotional wording. This site adds no advertising or analytics script. Catalogue search runs in your browser, and the optional theme choice is stored locally. Hosting and linked services apply their own policies.
The website source is public. Report a stale link or unclear first-run instruction there; product-specific bugs belong in the product repository.