Malicious or compromised modules
Treat guest code and its supplied data as untrusted.
SECURITY MODEL
Deny by default. Validate every grant.
The security model focuses on explicit authority, constrained operations and proof that denied access cannot bypass the broker.
Threat model
Overbroad permissions
Require exact module and resource scopes and minimize grant lifetime.
Broker escape
Test filesystem traversal, symlink races, network redirection and malformed requests.
Resource exhaustion
Bound CPU, memory, deadlines and concurrency outside the guest’s control.
Evidence alteration
Protect signing material and externally anchor audit evidence where appropriate.
Operator error
Support clear revocation, rollback and secure configuration defaults.
What is not claimed
OSR is not presently represented as a production-secure sandbox, replacement for PHP security updates, independently certified runtime, or comprehensive protection against operating-system compromise.
Prototype-local checks do not prove resistance to privilege escalation, compromised hosts, supply-chain attacks, concurrency races or deployment misconfiguration.
Security reporting
Do not disclose suspected vulnerabilities in a public issue. The repository includes a SECURITY.md policy for maintainers. A dedicated coordinated-disclosure channel should be established before public release.