Security reports are welcome for the SDK, its CLI, schemas, templates, and documentation. The public contract intentionally limits packages to declarative JSON so they cannot execute plugin-supplied code.

The SDK is not the host application. Host installation policy, trusted publisher admission, credential storage, and runtime network enforcement are implemented separately by the host and cannot be changed through this project.

Please do not disclose a suspected vulnerability in a public issue before it has been assessed. Use the private security-reporting channel offered by the repository host, or contact the maintainers through the repository's listed security contact. Include:

• affected SDK/CLI version and operating system;
• a minimal reproducible package or command;
• expected and actual behavior;
• impact assessment; and
• a safe proof of concept, without private keys, credentials, or user data.

Maintainers will acknowledge a report, assess reproducibility and impact, and coordinate a fix and disclosure timeline. Do not test against systems you do not own or have permission to assess.

Do not weaken these boundaries in contributions or package designs:

• only public HTTPS origins on port 443;
• one declared origin, equal to baseUrl;
• same-origin direct .funscript assets only;
• no executable module, native component, script injection, or dynamic loader;
• no private, loopback, link-local, or literal-IP provider origin; and
• no claim that SDK signature verification equals host trust.

See the threat model for assumptions and residual risk.