@feathery/react@2.89.0
React library for Feathery
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malicious behavior was confirmed, but runtime execution of a remotely served JavaScript module without integrity verification remains an unresolved security risk. The scanner's claimed decoded-payload behavior was not supported by the inspected decode path.
Decision evidence
public snapshot- The browser bundles construct dynamic imports for JavaScript served from a remote CDN.
- The remotely imported pdf.js code is not integrity-pinned in the package artifact.
- package.json has no npm preinstall, install, or postinstall hook.
- The prepare hook is a Husky development hook, while prepublishOnly only builds the package.
- The observed Base64 decode is for audio bytes, not decoded code execution.
- No credential harvesting, filesystem access, shell execution, or covert endpoint was confirmed.
Source & flagged code
7 flaggedPackage source references dynamic code evaluation.
dist/fthry_pdfjsLoader.CRkrFcJY.jsView on unpkg · L27Package source references dynamic require/import behavior.
dist/fthry_index.B2c1W0ze.jsView on unpkg · L271Findings
Affected versions and remediation
This report applies to @feathery/react@2.89.0.
See all versions of @feathery/react for other recorded verdicts.
- Review the evidence and your use of @feathery/react@2.89.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.