@embarkai/ui-kit@0.6.17
React UI components and hooks for embarkAI authentication and Account Abstraction
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe reported credential flow is feature-triggered and sends an Embark access token to the package’s own API. The manifest shows no install hook, and the inspected iframe message handler validates origins.
Decision evidence
public snapshot- The manifest describes a React UI kit for embarkAI authentication and account abstraction.
- The package scripts shown are build and development tasks; no install lifecycle hook is declared.
- The iframe’s on-ramp API defaults to `https://api.embarkai.io/on-ramp/api`.
- On-ramp requests attach an access token as a bearer token to that API.
- The library passes its access token to the iframe when an on-ramp query is invoked.
- The iframe validates message origins and rejects unauthorized origins.
- The flagged token-bearing traffic is consistent with the package’s authentication and on-ramp features; no unrelated credential source or collector was identified.
Source & flagged code
13 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/iframe/assets/main-DvSssncy.jsView on unpkg · L68Package source references dynamic code evaluation.
dist/iframe/assets/main-DvSssncy.jsView on unpkg · L6323Findings
Affected versions and remediation
This report applies to @embarkai/ui-kit@0.6.17.
See all versions of @embarkai/ui-kit for other recorded verdicts.
- Review the evidence and your use of @embarkai/ui-kit@0.6.17 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.