SecureToolKit has not published a stable public release. Security review is currently focused on the latest main RC candidate and the frozen protocol baselines it identifies.

Use GitHub private vulnerability reporting for this repository when it is enabled. Do not open a public issue containing exploit details.

If private vulnerability reporting is not yet available, open a public issue containing only a request for private maintainer contact. Do not include the vulnerability, affected inputs, credentials, customer information, raw prompts, or proof-of-concept details in that issue.

Include, when safely possible:

• the exact commit or tag;
• the affected API or protocol transition;
• the security invariant that may be violated;
• minimal reproduction steps using synthetic data;
• expected and observed behavior;
• impact and prerequisite assumptions; and
• whether the issue is already known publicly.

The project does not currently promise response or remediation times. Enabling and verifying the private GitHub reporting route is a public-release operations requirement.

• model-controlled content creating or broadening authority;
• authorization, confirmation, tool, schema, policy, or Host-boundary substitution;
• fail-open handling of unknown, missing, duplicate, malformed, or stale input;
• capability or resource escalation;
• replay-identity or Consumption-binding weakness;
• nondeterministic security decisions;
• privacy leakage in errors or diagnostics;
• public construction of controlled authority evidence; and
• a path from validation or Authorization to library-owned Execution.

SecureToolKit is not a complete production authorization deployment. The Host must provide and protect authentication, trusted time, cryptographic authenticity where required, durable replay handling, atomic single-use Consumption, revocation, audit persistence, secrets, networking, storage, and Execution.

The package contains no tool executor. Validation is pure and non-consuming. Human confirmation is evidence bound to an exact operation; it is not authentication and does not execute a tool.

Use synthetic fixtures. Never submit secrets, access tokens, private keys, personal data, production records, customer prompts, or data from systems you do not own or have permission to test.