mynd

mynd is a security-first, cross-platform Rust image crate designed for bounded resource use, deterministic behavior, and deployment from embedded no_std systems through desktop and server applications.

The project is in its current 0.2.1 specification-corpus phase. The workspace, security policy, verification gates, crate boundaries, scope contract, and standards ledger exist; image decoding and encoding APIs do not yet exist. The release plan defines the incremental path to the first production-ready 1.0.0 release.

Install

Most applications should depend on the facade crate with only the capabilities they need:

[dependencies]
mynd = { version = "0.2.1", default-features = false }

The default feature set is intentionally empty.

Capability status

Each release must satisfy its stated verification and security exit criteria; future capabilities are not considered available merely because they appear on the roadmap. Exact scope and public claim words are defined by the scope and claim contract.

Design goals

• no_std from the first release, with alloc and std kept behind explicit feature boundaries.
• Bounded allocation, dimensions, frame counts, metadata, nesting, and work budgets before parsing untrusted image data.
• Panic-free handling of malformed input and checked arithmetic throughout size, stride, offset, and allocation calculations.
• No hidden I/O, threads, global mutable state, platform assumptions, or mandatory runtime dependencies in the core path.
• Small, focused workspace crates instead of source files larger than 500 lines or monolithic implementation crates.
• Stable behavior across Linux, Windows, BSD, macOS, Android, and iOS, while preserving a path to future Aesynx support.

Features

Format and processing capabilities will be added as narrowly scoped opt-in features only when their release gates are complete.

Rust Version Support

The minimum supported Rust version is Rust 1.90.0. New deployments should use the pinned stable Rust 1.97.1 until the toolchain policy is updated.

Compatibility evidence for 0.2.1:

The compatibility policy is documented in toolchain policy.

Workspace

Application-facing APIs should enter through mynd. Support crates are published separately for workspace architecture and expert use, but are not the default integration surface.

Verification

Run the repository gate locally with the pinned development toolchain:

rustup run 1.97.1 scripts/checks.sh

The repository gate covers formatting, lints, tests, documentation, no_std builds, MSRV checks, dependency policy, and package contents. The full release gate and CI additionally run vulnerability auditing, the complete Rust and platform matrices, latest-tool checks, and SBOM verification. See toolchain policy for the full command matrix.

Security

Treat all image input as hostile. Mynd's security work starts before format implementation and is governed by:

• Security policy
• Threat model
• Supply-chain security
• Unsafe code policy
• Security controls

Please report vulnerabilities privately as described in the security policy.

Specifications and implementation plans

Mynd implementations must be traceable to authoritative format specifications, errata, and recorded security limits. The repository maintains:

• Specification corpus and reproduction workflow
• Tracked-source legal disposition review
• Specification source ledger
• Standards and errata ledger
• Scope and claim contract
• Corpus provenance schema
• Specification source policy
• Implementation plan
• Version plan
• Release process

License

Licensed under either of:

• Apache License, Version 2.0
• MIT License

at your option.