@embarkai/ui-kit@0.4.124
React UI components and hooks for EmbarkAI authentication and Account Abstraction
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection resolved the scanner’s credential and dynamic evaluation flags as application behavior: Google Drive access follows Google’s OAuth consent flow, and the dynamic function call is in WebAssembly glue. The manifest has no install lifecycle hook, and the inspected Radix dependencies are UI component bundles.
Decision evidence
public snapshot- package.json exposes UI entrypoints and contains build scripts but no install lifecycle hook.
- dist/index.js routes authentication and service calls through configurable EmbarkAI service URLs.
- The Google Drive integration requests an OAuth token through Google’s consent flow and uses it for Google Drive operations.
- The sampled dependency files are React UI components from Radix UI.
- The iframe bundle’s dynamic Function call is part of WebAssembly JavaScript bindings.
Source & flagged code
14 flaggedFindings
Affected versions and remediation
This report applies to @embarkai/ui-kit@0.4.124.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.4.124 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.