base64-ng 1.3.0

[eldryoth]

base64-ng v1.3.0

1.3.0 is the implementation-completion release for the original full Base64 scope.

Added

• Admitted normal strict SIMD decode for Standard and URL-safe alphabets:
  • x86/x86_64 AVX-512 VBMI
  • x86/x86_64 AVX2
  • x86/x86_64 SSSE3/SSE4.1
  • little-endian AArch64 NEON
• Added strict const decode helpers for fixed static inputs with recoverable Result errors.
• Added base64-ng-tokio manual AsyncRead streaming adapters with fixed buffers.
• Added bounded Tokio helper APIs.
• Expanded serde companion modules for Standard, Standard no-pad, URL-safe, URL-safe no-pad, MIME, and PEM profiles.
• Added advanced optional Kani proof script for expensive background verification.

Security / Hardening

• Strict SIMD decode runs only after whole-input scalar validation, preserving scalar error shape and canonicality checks.
• Wrapped decode, legacy whitespace decode, custom alphabets, bcrypt/crypt profiles, in-place decode, no_std, wasm runtime dispatch, and ct secret decode remain scalar.
• Hardened Tokio cleanup paths and reader error handling.
• Expanded malformed-input, scalar-equivalence, dispatch-boundary, fuzz, benchmark, unsafe-inventory, and backend-evidence coverage.
• Refreshed wasm posture docs: wasm simd128 remains compile/codegen evidence only, not runtime-dispatched.
• Extended CI Miri timeout for the full verification suite.

Documentation

• Refreshed README examples and install snippets for 1.3.0.
• Synced all workspace crate versions and release metadata to 1.3.0.
• Added post-1.3.0 roadmap slices for async writer adapters, broader SIMD surfaces, wasm dispatch review, niche architectures, and RVV research.

Notes

Async writer adapters are still intentionally deferred. Constant-time-oriented secret decode remains scalar by design unless a future side-channel evidence package admits otherwise.

---

This discussion was created from the release base64-ng 1.3.0.