QEV status, versions & test matrix

Last updated: 2026-07-29 · Purpose: one place for versions and test counts so marketing pages never invent numbers.

Product hierarchy (one stack)
1. Envelope Core — portable Vault V2 (browser, desktop, CLI)
2. Capture Gateway — customer-controlled event → package pipeline
3. Connectors — webhook, portal, photo/file, file-watch (more planned)
4. Flow Packs — Field Service (pilot); AI/legal/devops packs planned
5. Verify — multi-verdict package review + seal certificates
6. Control Plane — optional; not required for local pilot · no customer plaintext

Capability labels

Label	Meaning
Available	Works today on a public or pilot surface
Preview	Controlled-use; limited trust model; not enterprise-hardened
Planned	Designed / scaffolded; not ready for production claims
Not assessed	No independent third-party security audit completed

Component matrix

Component	Version	Status	Tests (source)	Vault V2	Evidence Bundle V1
Product preview demo (site /app history)	0.29.0	Preview	258 (220 product + 38 vault-tool) — as published on main product page	—	—
Desktop / mobile apps (downloads)	0.29.0	Preview · unsigned installers	362 — download-page claim for that binary pipeline; different suite from the 258 product tests	R/W	Planned open
CLI npm package	0.30.0	Available	Built-in `qev self-test` + package `node --test` suite (historically documented as ~26 cases — not the same as 258/362)	R/W	Planned
Browser vault `/vault`	0.29.x / V2 format	Available	Included in vault-tool portion of product testing; crypto self-test in page	R/W	No
qev-platform gateway	0.3.x pilot	Preview pilot	Monorepo Vitest (packages + gateway) — run `pnpm test` in qev-platform; count is CI-generated, not hand-edited on marketing pages	Seals via V2	Write/verify
Qira Link	0.1.0-alpha	Sibling alpha	Separate product — not counted in QEV product 258	—	—

Why test counts differ

They are different codebases and suites, not “failed tests missing from the homepage.”

258 — product preview / policy-demo path (as stated on the main site).
362 — desktop binary pipeline claim on the downloads page.
CLI self-test — small focused suite for the npm package only.
qev-platform — separate Vitest monorepo for the commercial gateway.

Never mix these numbers into one “QEV has N tests” claim without naming the component.

Official package names (today)

Package	Name	Notes
CLI (published)	`@bryan237l/qev-cli`	Install: `npm i -g @bryan237l/qev-cli` · v0.30.0 on npm
Platform monorepo packages	`@imagineqira/qev-*`	Workspace packages in GitHub; not all published to npm yet
Future brand alignment	`@imagineqira/qev-cli`	Planned rename/publish; until then use `@bryan237l/qev-cli`

What is live on this host

Envelope Core (browser vault) — Available
Capture Gateway pilot — Preview
Field Service flow docs — Preview
Trust program — Compatible / Pilot certs only; no Protected badge
Audit status — Not independently assessed
Site integrity — Ed25519-signed manifest

What is not claimed

Not production-ready multi-tenant SaaS
No formal third-party security audit
No KMS/HSM · no formal key rotation/revocation
Installers not Apple-notarized / Authenticode-signed yet
No “QEV Protected Workflow” public badge yet

Source of this page: qev-platform · Gate A honesty · Update when versions change · Do not hand-edit counts on marketing pages without updating this matrix.