@feathery/react@2.77.1
React library for Feathery
AI Security Review
scanned 1mo ago · by lpm-firewall-aiCaller-selected destinations are not bound to the intended service when the component automatically forwards an existing session cookie. This warrants a credential-exposure warning rather than a malicious-package block.
Decision evidence
public snapshot- The public entrypoint exports AssistantChat, which accepts a caller-selected baseUrl.
- Without getJwt, chat headers copy the existing feathery_session_token cookie into X-Feathery-Session.
- Thread requests derive their destination from baseUrl and send those headers without a destination allowlist.
- Opening the chat triggers the thread-list request.
- The built-in form supplies the configured API origin, limiting the ordinary integration's exposure.
- No covert recipient or malicious intent was established.
- Supplying getJwt bypasses the automatic session-cookie forwarding.
Source & flagged code
7 flaggedPackage source references dynamic code evaluation.
dist/fthry_AssistantChat.BvP-a78C.jsView on unpkg · L10383Package source references dynamic require/import behavior.
dist/fthry_index.D7Q-9Ib-.jsView on unpkg · L271Findings
Affected versions and remediation
This report applies to @feathery/react@2.77.1.
See all versions of @feathery/react for other recorded verdicts.
- Review the evidence and your use of @feathery/react@2.77.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.