Skip to content

Security: skarm/xmlsec

Security

SECURITY.md

Security policy

The API is experimental. Full standards conformance and an independent security audit have not been established. No stable-release support or security response time is promised. Use a Go toolchain with security fixes that meets the requirements in go.mod.

Supported profiles and limitations are documented in compatibility. Applications must configure trust, signature coverage and resource access; see the API guide. Embedded keys and certificates do not establish trust. Transform execution has in-process limits, without OS isolation. Memory state/replay stores coordinate one process.

Reporting vulnerabilities

Use GitHub private vulnerability reporting if enabled. Its availability has not been confirmed. Otherwise, arrange a working private contact with the maintainer before sharing vulnerability details.

Include the affected revision, impact and a minimal synthetic reproduction. Keep exploit details and confidential documents out of public issues. Never include private keys or live tokens in a report.

There aren't any published security advisories