Open Source · Compatibility
Tested boundaries, not universal claims.
RuleOak distinguishes automated compatibility evidence from independent real-world integration evidence.
Runtime support
| Environment | Status | Boundary |
|---|---|---|
| Node.js 22 LTS | Tested | Full source/publish-readiness path in the documented matrix. |
| Node.js 24 LTS | Tested | Current supported LTS line and owner-Mac qualification path. |
| Node.js 26 Current | Compatibility signal | Useful signal; production-like use should prefer an LTS line. |
| ESM | Supported public package shape | CommonJS require() is not the primary supported surface. |
Integration paths
| Path | Evidence | Non-claim |
|---|---|---|
| Node.js SDK | Unit/integration tested | Cannot protect retained unguarded executors. |
| MCP stdio | Fixture/integration tested for documented JSON-RPC behavior | Not universal client/server compatibility. |
| MCP Streamable HTTP | Documented/fixture-tested supported path | Not a universal transport proxy. |
| Loopback REST | Local authorization path tested | Non-loopback needs explicit auth/TLS architecture. |
| OpenAI-style adapter | Normalization/authorization tested | Not an OpenAI network client. |
Report a compatibility result
After the public repository is live, report exact RuleOak/Node/client/server versions, integration path, sanitized reproduction, expected behavior and observed behavior. Do not include secrets/private evidence.