Evolext

[01] — Research-stage post-quantum readiness

Understand your cryptography.Plan your next step.

Evolext combines offline repository discovery with scoped readiness reviews and controlled software engineering work.

Inspect a sample Discuss a repository assessment

[02] — Synthetic laboratory sample · not a customer result

A finding you can inspect

An observation is the beginning of a question. Explore the evidence, its meaning, and what still needs human review.

Synthetic laboratory sample · not a customer resultv0.2.0 / JSON schema v2
Observed evidence High severity

RSA usage

Crypto.cs · Line 8

Recorded observationcall System.Security.Cryptography.RSA.Createdirect-api-usage
Rule
QS1001
Algorithm
RSA-2048
Detection confidence
0.99

Confidence describes the detection, not the probability that a deployed system is unsafe.

[01] Why it matters

This observation starts a review of public-key cryptography. Its purpose and the surrounding protocol determine which migration questions to ask.

[02] What remains unknown

Source presence does not establish deployed use, data confidentiality lifetime, or provider support. Human review must confirm the system context before choosing a change.

Read the original scanner recommendation

Original report text

RSA usage detected

Determine whether this RSA use provides key establishment, encryption, signatures, or another function. Assess ML-KEM for key establishment and ML-DSA or SLH-DSA for signatures only after confirming protocol and provider support.

This excerpt comes from the included six-language sample report. Complete coverage means its supported candidate inputs were analyzed; it does not mean a complete system inventory.

Open the full synthetic JSON report ↗

Local v0.2.0 prototype · public downloads unavailable

Explore the scanner ↗

[03] — The approach

From observation to a scoped decision.

  1. [01]

    Discover

    Input
    An authorized repository and agreed coverage.
    Activity
    Inspect supported source APIs and local dependency declarations.
    Deliverable
    Recorded observations, coverage boundaries, and evidence gaps.
  2. [02]

    Assess

    Input
    Reviewed findings and supplied system context.
    Activity
    Discuss ownership, data lifetime, vendor support, and migration constraints.
    Deliverable
    A prioritized set of questions and scoped next actions.
  3. [03]

    Prototype

    Input
    One agreed technical question and laboratory boundary.
    Activity
    Explore selected implementations and interoperability in a controlled environment.
    Deliverable
    A prototype record, test observations, and explicit limitations.

PQC-led technology studio

Three practical steps toward quantum readiness

Start by finding cryptographic dependencies, assess business and data risk, then migrate selected systems through controlled engineering work.

[01]

Crypto Inventory / PQC Readiness Scanner

A tool-assisted engagement that maps observable cryptographic use, ownership, dependencies, and evidence gaps.

Explore this service
[02]

Quantum-Safe Readiness Assessment

A business and technical assessment covering data longevity, vendor readiness, migration constraints, and priorities.

Explore this service
[03]

PQC Migration Service

Narrowly scoped architecture, laboratory prototypes, interoperability testing, and implementation support.

Explore this service

Evolext's current PQC work is assessment-, research-, and prototype-led. It does not certify compliance or guarantee protection against future quantum attacks.

Software engineering · supporting service

Secure application development with post-quantum readiness

Application engineering supported by dependency review and migration planning. Selected PQC integrations can be evaluated in a separately scoped laboratory prototype.

Explore application development

[05] — Scope and evidence

Understand the coverage boundary

  • No runtime, network, certificate, configuration, binary, or cloud scanning.
  • No complete dependency graph, CVE analysis, SBOM, or CBOM.
  • File-local analysis can miss wrappers, dynamic usage, unsupported syntax, and unknown packages.
  • A scan does not prove quantum safety, security, compliance, reachability, or cryptographic correctness.

Evidence and standards

Implementation level: local v0.2.0 prototype and synthetic fixtures. Knowledge reviewed: 8 August 2026; storefront reviewed: 11 October 2026. NIST FIPS 203 (ML-KEM), 204 (ML-DSA), and 205 (SLH-DSA) are algorithm reference standards, not certification of this scanner or your software. Source detection does not establish deployed usage or successful PQC negotiation.

NIST FIPS 203 / 204 / 205 ↗

[06] — The studio

Clear scope. Inspectable work.

Evolext is an independent technology studio for SaaS companies and SMEs. Research, assessment, and software engineering work start with a defined boundary and evidence that can be reviewed.

How Evolext works ↗
Deep Insights

Insights & Thought Leadership

Expert perspectives on business transformation

Ready to Start?

Start with a defined repository scope

Describe the software you own and the decision you need to make. Agree evidence and handling boundaries before an assessment.

evolext@hotmail.comInquiries are reviewed before Evolext responds.

Discuss your repository

Share your languages and assessment goal. Do not include code, secrets, or confidential reports.