@feathery/react@2.115.0
React library for Feathery
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged credential handling and account connection code fit the package’s Feathery form integration, and the Base64 strings are ad-block selector data. I found no automatic account mutation, unrelated credential transfer, or harmful install behavior.
Decision evidence
public snapshot- The package exports compiled React entry points; its prepublishOnly script builds the package and prepare runs Husky.
- The browser helper reads the Feathery session cookie and attaches it to requests made through the Feathery API helper; the listed API hosts are Feathery domains.
- Account connection requires a popup and calls the account-connect flow after that permission check.
- The Base64 strings flagged in the CJS bundle are ad-block filter selectors, not a concealed runtime endpoint.
- Segment tracking is conditional on configured integration metadata; user IDs and submitted fields are included only under configured conditions.
Source & flagged code
6 flaggedBrowser source reuses an authenticated session to collect identity data and mutate account settings while reporting externally.
umd/index.jsView on unpkg · L1Package source references a known benign dynamic code generation pattern.
umd/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @feathery/react@2.115.0.
See all versions of @feathery/react for other recorded verdicts.
- Review the evidence and your use of @feathery/react@2.115.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.