@upcoming/multichain-widget@0.13.3
``` npm install @upcoming/multichain-widget ```
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe manifest exposes built widget bundles and declares no install hooks. Although a bundled chunk reads RAINBOW_PROVIDER_API_KEY, the source uses it as an API key for enhanced-provider.rainbow.me, which matches the Rainbow provider integration and does not establish credential exfiltration.
Decision evidence
public snapshot- The manifest has no install lifecycle scripts; it exposes bundled widget entry points.
- The flagged environment variable is specifically RAINBOW_PROVIDER_API_KEY and is used as an x-api-key for enhanced-provider.rainbow.me, Rainbow's provider endpoint.
- The source initializes a Rainbow fetch client; the inspected code does not show this value being sent to an unrelated host.
Source & flagged code
6 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.es-BgSZaIrD.mjsView on unpkgPackage source references dynamic require/import behavior.
dist/index.es-BgSZaIrD.mjsView on unpkg · L1180Findings
Affected versions and remediation
This report applies to @upcoming/multichain-widget@0.13.3.
See all versions of @upcoming/multichain-widget for other recorded verdicts.
- Review the evidence and your use of @upcoming/multichain-widget@0.13.3 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.