| Version | Supported |
|---|---|
| 1.0.x | ✅ Active support |
If you discover a security vulnerability in the IdentArk TypeScript SDK, please report it responsibly:
- Do not open a public issue — vulnerabilities should not be disclosed publicly until a fix is available.
- Email security reports to:
security@identark.io - Include:
- A description of the vulnerability
- Steps to reproduce
- Potential impact assessment
- Suggested fix (if any)
We aim to respond to security reports within 48 hours and release patches within 7 days for critical issues.
The SDK implements the following security controls:
- Zero runtime dependencies — minimal supply chain attack surface
- No secret logging — API keys and tokens are never logged to console
- Cost caps — Built-in spending limits prevent runaway costs
- Path validation — File operations are restricted to the workspace directory
- Strict TypeScript — Type safety prevents many classes of bugs
- Integration tests against a live control plane are planned but not yet available.
- LlamaIndex, CrewAI, LangGraph, and Gemini framework integrations are planned — LangChain.js is available now.
// Always use environment variables for API keys
const gateway = new DirectGateway(
new OpenAI({ apiKey: process.env.OPENAI_API_KEY }),
"gpt-4o"
);
// Set cost caps in production
const gateway = new DirectGateway(client, "gpt-4o", undefined, 0.50);We follow a coordinated disclosure model:
- Reporter submits vulnerability privately
- We acknowledge receipt within 48 hours
- We investigate and develop a fix
- We release the fix and publicly disclose the vulnerability with credit to the reporter
- We request a CVE for critical vulnerabilities
- Primary:
security@identark.io - GPG Key: Available on request