@feathery/react@2.53.2
React library for Feathery
AI Security Review
scanned 4mo ago · by lpm-firewall-aiDirect source inspection found only package-aligned browser SDK behavior. Scanner hits for environment access and dynamic code stem from build/runtime compatibility code, while no concrete malicious chain was found.
Decision evidence
public snapshot- `package.json` has no preinstall/install/postinstall hook; `prepare` only invokes Husky.
- `cjs/index.js` imports a packaged React entry chunk and exports SDK components/helpers; no import-time shell or file action found.
- No Node builtin `child_process`, `fs`, `vm`, or network-module require was found in shipped JS.
- `cjs/fthry_index.BiPct8bU.js` uses `process.env.BACKEND_ENV` only to select a Feathery backend environment.
- Dynamic `Function('return this')` calls in `cjs/fthry_index.BiPct8bU.js` are bundled global-object compatibility helpers.
- Network URLs in `cjs/fthry_index.BiPct8bU.js` are Feathery API configuration and browser integrations, activated by SDK runtime features.
Source & flagged code
5 flaggedPackage source references a known benign dynamic code generation pattern.
umd/602.ddda17ac6b2cabb3d639.jsView on unpkg · L1Package source references dynamic require/import behavior.
dist/fthry_index.ChaDIUkK.jsView on unpkg · L3657Findings
Affected versions and remediation
This report applies to @feathery/react@2.53.2.
See all versions of @feathery/react for other recorded verdicts.
- Review the evidence and your use of @feathery/react@2.53.2 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.