Security and trust
WrenLore is built for operational knowledge. Security work is part of the product, not a badge added to the marketing page.
Deployment boundary
WrenLore runs on infrastructure controlled by the operator. It does not require a mandatory WrenLore cloud control plane. Operators remain responsible for TLS, host security, backups, network policy and production monitoring.
Identity and access
WrenLore supports local authentication and enterprise SAML flows, with role and page-level access controls. MCP access uses scoped credentials tied to a user identity rather than an anonymous shared agent account.
Maintenance
The project tracks vulnerabilities in its dependency stack and inherited community code. Public releases and security maintenance are recorded in the GitHub repository.
Report a vulnerability
Do not open a public issue for an undisclosed vulnerability. Use the private security reporting channel in the GitHub repository.
Open GitHub Security