If you discover a security vulnerability in this project, please report it responsibly.
Do not open a public GitHub issue for security vulnerabilities.
Instead, email: security@commandlayer.org
Please include:
- A description of the vulnerability
- Steps to reproduce the issue
- Potential impact assessment
- Suggested fix (if any)
We will acknowledge receipt within 48 hours and provide a detailed response within 7 days.
| Version | Supported |
|---|---|
| 1.0.x | Yes |
This runtime handles cryptographic signing and verification. Operators should:
- Protect signing keys -- never expose
RECEIPT_SIGNING_PRIVATE_KEY_PEM_B64in logs or client responses. - Gate debug routes -- set
DEBUG_ROUTES_ENABLED=0(default) in production, or protect withDEBUG_BEARER_TOKEN. - Restrict CORS -- configure
CORS_ALLOW_ORIGINSto specific origins; never use*in production. - Enable SSRF guard -- keep
ENABLE_SSRF_GUARD=1(default) and useALLOW_FETCH_HOSTSto restrict outbound domains. - Use HTTPS -- always deploy behind TLS termination in production.
- Pin dependencies -- use
npm ciwith the lockfile for reproducible builds.