@copilotkit/runtime@1.79.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 20d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed credential transfers use the configured Intelligence endpoint with a CopilotKit service default. The flagged bridge resolves to local runtime modules, so the inspected source does not establish malicious behavior.
Decision evidence
public snapshot- package.json points to the distribution entrypoints and lists development scripts; it contains no install lifecycle hook.
- The Intelligence client defaults to CopilotKit’s API and uses the API URL and key supplied in its configuration; its documented custom endpoint is explicitly paired with a caller-supplied key.
- Both module formats send that configured key to the configured API for learned-skill requests; the calls use the client’s API URL and reject redirects.
- The flagged CommonJS handler bridge loads local runtime and client modules, and the handler requires an Intelligence runtime configuration.
Source & flagged code
3 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.79.1.
See all versions of @copilotkit/runtime for other recorded verdicts.
- Review the evidence and your use of @copilotkit/runtime@1.79.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.