@feathery/react@2.114.1
React library for Feathery
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest’s install hooks perform build and repository setup tasks. Runtime review resolved the flagged analytics transport and user-key update as SDK operations, with no inspected source showing an unrelated credential recipient or automatic account mutation.
Decision evidence
public snapshot- The manifest routes imports to the CommonJS and browser SDK bundles; its install hooks run the build or Husky setup.
- The SDK’s default API hosts belong to Feathery, and its session header is attached by the API request helper.
- Analytics sends event batches to its configured host using its analytics write key; credentials are passed from analytics configuration.
- The user-key update method sends a PATCH to the Feathery user endpoint, and its caller requests that update only when the merge option is enabled.
- The inspected entry bundles and chunks load React, form UI, and supporting libraries; the flagged chunks do not establish an attack.
- The source includes browser fingerprinting and analytics functionality, but the inspected paths do not show those features exporting Feathery session credentials to an unrelated recipient or making an unrequested account change.
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.114.1.
See all versions of @feathery/react for other recorded verdicts.
- Review the evidence and your use of @feathery/react@2.114.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.