OpenTine · v0.44.0
Compatibility
Compatibility is defined by file formats and protocol capabilities. A CLI version number or an open-ended dependency range alone does not establish interoperability. Reviewed 7 November 2026.
| Surface | Required capability | Status |
|---|---|---|
| Core CLI | Read portable v5; repository v3; legacy v4 output | Shipped in the pinned v0.44.0 release |
| TypeScript verifier | Reader and verifier ops, including v5 and signatures | GA; all reader and verifier vectors pass with reason-code agreement |
| Legacy TUI | Current core API and v5 reader support | Does not work with the current core; use the CLI |
| Legacy GUI | Current core API and v5 reader support | Does not work with the current core; use the CLI |
| opentine-web | Browser verification and shared viewer | Planned; not available here |
No working current visual companion is claimed. The legacy TUI and GUI are not recommended installation paths. The new shared viewer is on the roadmap.
Formats
Portable .tine files default to v5, since 0.42. --for-legacy writes v4. The repository format is .tine/ v3. tine evidence export writes v4. Readers before 0.40 refuse v5. Bundles made with --transparency require 0.44 or newer.
Verifier scope
The suite contains 683 vectors, including 225 refusal cases, across 40 ops. The TypeScript verifier answers every reader and verifier vector with full reason-code agreement. Four writer-side redaction ops are not answered: the verifier does not rewrite content. Node usage requires Node 20.19 or newer.
Sources: CLI format policy, SPEC, 0.44 changelog. The published TUI description targets legacy portable v2 and a core range below the current release. The published GUI description describes portable v2 and testing against an older core. Neither establishes v5 support. The M0 compatibility audit reports both as non-working with the current core; a new capability demonstration is required before recommending either.