waaseyaa/state

Key-value state storage for Waaseyaa

Maintainers

Package info

github.com/waaseyaa/state

pkg:composer/waaseyaa/state

Transparency log

Statistics

Installs: 10 708

Dependents: 2

Suggesters: 0

Stars: 0

Open Issues: 0

Security

Advisories: 0

Aikido package health analysis

v0.1.0-alpha.296 2026-08-19 17:27 UTC

Requires

Requires (Dev)

GPL-2.0-or-later dadd3dd27a7db2c8ed6db83bcddcf97a3215c3bd

Published on Packagist.org on 2026-08-19 17:53 UTC

This package is auto-updated.

Last update: 2026-08-19 17:53:39 UTC

README

SQL-backed and in-memory application state.

SqlState requires a caller-owned 32-byte HMAC key. It stores serialized values only inside a strict versioned HMAC-SHA-256 envelope and verifies that envelope before every deserialization. MemoryState is unchanged. The state package does not register a built-in application-master purpose because no production provider composes SqlState; an application that persists it must own and document that key's lifecycle explicitly.

Existing SQL state values are invalidated at cutover: stop application workers, clear the state table, deploy the keyed reader/writer, and allow application state to rebuild. SqlState does not accept unsigned rows.

Changing the caller-owned HMAC key invalidates all persisted SQL state values.