@copilotkit/runtime@1.63.1
<img src="https://github.com/user-attachments/assets/0a6b64d9-e193-4940-a3f6-60334ac34084" alt="banner" style="border-radius: 12px; border: 2px solid #d6d4fa;" />
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe flagged primitives are consistent with a server-side AI runtime: configured model/cloud calls and disclosed sampled telemetry. Direct inspection found no lifecycle hook, stealthy payload loading, filesystem/agent-control writes, destructive action, or concrete exfiltration chain.
Decision evidence
public snapshot- Runtime constructors emit sampled telemetry after initialization.
- Legacy telemetry includes configured cloud public-key metadata.
- Intelligence handlers send user-request data to configured API URLs.
- package.json has no preinstall, install, postinstall, or prepare hook.
- No packaged runtime file-write, shell, eval, VM, or child-process execution found.
- Telemetry is disclosed, sampled, and supports COPILOTKIT_TELEMETRY_DISABLED and DO_NOT_TRACK.
- Dynamic import only loads the fixed optional @copilotkit/channels-intelligence module.
- Intelligence requests require caller-provided runtime configuration and credentials.
- Bundled skill is documentation only; it does not alter agent configuration.
Source & flagged code
2 flaggedPackage source references dynamic require/import behavior.
dist/langgraph.cjsView on unpkg · L1Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/v2/runtime/handlers/intelligence/annotate.cjsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @copilotkit/runtime@1.63.1.
See all versions of @copilotkit/runtime for other recorded verdicts.
- Review the evidence and your use of @copilotkit/runtime@1.63.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.