@feathery/react@2.106.1
React library for Feathery
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe bundle contains a concrete request-tampering capability in a DocuSign signing flow, while nearby code suggests a possible draft workflow. That unresolved behavior warrants a warning, but the inspected source does not establish a broader attack or justify blocking publication.
Decision evidence
public snapshot- The UMD bundle is exposed through the package's jsDelivr entry.
- The UMD bundle replaces XMLHttpRequest.send and changes DocuSign signing status data to "sent".
- The altered request data is passed to the original send method.
- The same bundle changes the DocuSign dialog to draft-related wording, suggesting a specialized workflow; no broader attack was established.
- The manifest identifies the package as a React library and its standard module entries point to CJS and ESM bundles.
- The inspected CJS file begins with imports of React and related UI modules.
Source & flagged code
6 flaggedPackage source references a known benign dynamic code generation pattern.
dist/fthry_AssistantChat.Zw4b54hO.jsView on unpkg · L10387Package source references dynamic require/import behavior.
dist/fthry_index.BEzf6zno.jsView on unpkg · L271Findings
Affected versions and remediation
This report applies to @feathery/react@2.106.1.
See all versions of @feathery/react for other recorded verdicts.
- Review the evidence and your use of @feathery/react@2.106.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.