@feathery/react@2.87.0
React library for Feathery
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe high-risk detections resolve to normal bundled browser functionality: a pinned PDF renderer import, authenticated SDK requests, and base64 byte handling. The package has no automatic registry install hook or concrete malicious behavior.
Decision evidence
public snapshot- The manifest declares a publication build hook, not a preinstall, install, or postinstall hook.
- The PDF loader dynamically imports a pinned pdfjs module from jsDelivr at runtime.
- The main browser bundle reads a Feathery session cookie and sends it as an API request header.
- The semantic-limit artifact is a CommonJS bundle that imports the primary implementation.
- The AssistantChat artifact decodes base64 chunks into byte arrays for a queued segment.
- The reported new artifact starts with ordinary React and UI module imports.
- No automatic registry install hook or self-dependency was found.
- The PDF import is a visible, version-pinned dependency load for PDF rendering.
- The AssistantChat base64 operation creates bytes and queues them; it does not evaluate decoded content.
- The cookie use is explicit SDK authentication for the request URL, not collection sent to an unrelated endpoint.
- No source evidence established credential harvesting, shell execution, persistence, destructive behavior, or covert exfiltration.
Source & flagged code
8 flaggedPackage source references dynamic code evaluation.
dist/fthry_pdfjsLoader.CRkrFcJY.jsView on unpkg · L27Package source references dynamic require/import behavior.
dist/fthry_index.DJmDb7d6.jsView on unpkg · L74Findings
Affected versions and remediation
This report applies to @feathery/react@2.87.0.
See all versions of @feathery/react for other recorded verdicts.
- Review the evidence and your use of @feathery/react@2.87.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.