@feathery/react@2.102.0
React library for Feathery
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source shows service-session credential forwarding to a caller-selected destination without an enforced destination restriction on that credential. This warrants a warning for dangerous capability, while the evidence does not support malicious intent or publication blocking.
Decision evidence
public snapshot- The public entrypoint exports AssistantChat, which accepts a caller-selected baseUrl.
- Without getJwt, AssistantChat reads the existing Feathery session cookie and adds it to request headers.
- Thread requests use the supplied baseUrl origin and send those headers through fetch.
- Opening the assistant activates thread fetching; supplying getJwt bypasses the cookie-based header branch.
- The request wrapper returns existing options unchanged for destinations outside its backend origin check.
- The built-in form caller selects the Feathery API origin.
- The inspected dynamic loader fetches a pinned PDF renderer for document previews; no concrete malware behavior was identified.
Source & flagged code
7 flaggedPackage source references dynamic code evaluation.
dist/fthry_AssistantChat.DAealcHs.jsView on unpkg · L10388Package source references dynamic require/import behavior.
dist/fthry_index.CWgc_dqo.jsView on unpkg · L3657Findings
Affected versions and remediation
This report applies to @feathery/react@2.102.0.
See all versions of @feathery/react for other recorded verdicts.
- Review the evidence and your use of @feathery/react@2.102.0 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.