Security and safety
Hostwright 0.0.2-dev is not production-ready. The v0.0.2 release still
requires current-source runtime, security, and signed-artifact qualification.
Read the core security policy
and security safety reference
for the current source-of-truth details.
Runtime changes
Section titled “Runtime changes”Runtime lifecycle commands require a current dry-run plan and exact confirmation. The authenticated local daemon revalidates the selected manifest, provider capability, ownership, and request authority before effects. Cleanup uses a separate confirmation and only removes exact eligible Hostwright-owned resources. Ambiguous ownership or state fails closed.
Data and diagnostics
Section titled “Data and diagnostics”State and diagnostics remain local. Support bundles show a preview and require confirmation; they include bounded, redacted information and can be encrypted before writing. Hostwright does not upload bundles or run a hosted telemetry service. Review every bundle before sharing because local identifiers and configuration context can remain sensitive.
Do not put plaintext credentials in manifests, logs, fixtures, screenshots, or public issue reports. Use supported typed secret references and inspect commands, image references, ports, mounts, and environment before confirming an untrusted manifest.
Reporting a security issue
Section titled “Reporting a security issue”Do not publish secrets, credentials, private hostnames or paths, diagnostic bundles, live-resource identifiers, or exploit details in a public issue. The project has not published a dedicated private security contact. If a report contains sensitive details, request a private maintainer contact before sharing them.