@copilotkit/runtime@1.70.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 2mo ago · by lpm-firewall-aiStatic inspection found normal runtime integrations and no concrete malicious execution chain. The scanner signals are explained by packaged AI-service networking, environment configuration, and static module imports.
Decision evidence
public snapshot- The manifest exposes runtime entrypoints and development scripts; it has no install lifecycle hook.
- The annotation handler sends a caller-provided annotation only after a runtime and authenticated user are resolved.
- The optional guardrails feature posts conversation content to a configured CopilotKit cloud endpoint.
- No install-time execution, self-dependency, shell execution, file mutation, or persistence was found.
- The network calls are runtime features of the CopilotKit service and use configured API credentials or request headers.
- The LangGraph finding is ordinary static module loading, not a computed or remote payload load.
Source & flagged code
4 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.70.1.
See all versions of @copilotkit/runtime for other recorded verdicts.
- Review the evidence and your use of @copilotkit/runtime@1.70.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.