Crypto-View

Roadmap

What we are working on next. Everything already available is on the documentation page.

Languages

LanguageStatus
JavaJCA/JCE, BouncyCastle Available
Pythonpyca/cryptography, PyCryptodome, PyJWT, paramiko Available
JavaScript and TypeScriptNode crypto, WebCrypto, JOSE, node-forge, @noble Available
Gocrypto/*, golang.org/x/crypto Available
C and C++OpenSSL, Mbed TLS and PSA, wolfSSL, libsodium, Windows CNG, PKCS#11, liboqs, GnuTLS, Crypto++, Botan Available
C#.NET cryptography, BouncyCastle.NET Planned
RustRustCrypto, ring, rustls Planned
Kotlin and Scalavia the JCA Planned
Ruby, PHP, SwiftOpenSSL bindings, CryptoKit Planned
Terraform and KubernetesKMS keys, cert-manager, service mesh Planned

Output formats

5.19.0 writes CycloneDX 1.7, SARIF 2.1.0, a GitLab Code Quality report and a Markdown summary. All come out of the same scan, so the numbers in one cannot disagree with another.

FormatStatus
CycloneDX 1.7 CBOMThe full inventory: every algorithm as a cryptographic asset, with each occurrence Available
SARIF 2.1.0GitLab's Security tab and merge request widget (Ultimate), GitHub code scanning, an editor's Problems panel Available
GitLab Code QualityWhat a merge request introduces and fixes, in the merge request on every GitLab tier Available
Markdown summaryWritten to a CI job summary, for the reader who did not run the tool Available

Pipelines

PlatformStatus
GitLab CI/CD Available

Editors

EditorStatus
Visual Studio CodeFindings in the Problems panel, the posture in the side bar, only what is new on request; delivered with QComply Available
Availableroll">
CapabilityStatus
Crypto-agility grading Planned
Scan comparison--new: only what appeared since the last run or a baseline; crypto-view history: the posture over time Available
Data-lifetime input Planned
Read-only API Planned

Requests: contact@qcomply.tech.