@feathery/react@2.71.0
React library for Feathery
AI Security Review
scanned 3mo ago · by lpm-firewall-aiStatic source inspection found no concrete malicious chain or install-time execution. Scanner signals map to documented PDF.js dynamic import, hosted Feathery APIs, and explicit custom-component behavior.
Decision evidence
public snapshot- Lifecycle scripts are build/prepublish tooling and Husky; no install/postinstall payload is defined.
- API configuration names Feathery-owned service endpoints.
- `new Function` is documented and limited to a pinned jsDelivr PDF.js dynamic import.
- The custom-component loader derives imports from supplied component code, not hidden package data.
- Browser runtime includes network, storage, and authentication SDK functionality expected of a hosted form library.
- Custom components can explicitly request external imports, a user-configured capability rather than a covert payload.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/fthry_index.7w1XP0g7.jsView on unpkg · L31Package source references a known benign dynamic code generation pattern.
dist/fthry_index.7w1XP0g7.jsView on unpkg · L46Findings
Affected versions and remediation
This report applies to @feathery/react@2.71.0.
See all versions of @feathery/react for other recorded verdicts.
- Review the evidence and your use of @feathery/react@2.71.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.