@feathery/react@2.113.0
⚠ Under reviewReact library for Feathery
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe credential-related matches inspected are analytics delivery code, but the large UMD entrypoint's reported account-setting behavior remains unresolved after targeted review. Manual review is needed to establish whether that behavior is reachable and authorized.
Decision evidence
public snapshot- The manifest routes consumers to CJS, ESM, and UMD builds; its prepare hook runs Husky and prepublishOnly runs the build.
- The inspected analytics code sends event batches through configured HTTP delivery and supports a page-unload flush.
- The bundle wires the batching or standard analytics transport to configured delivery settings.
- The inspected analytics transport is connected to Segment analytics initialization; these excerpts do not establish that it exports saved service credentials.
- The UMD build is a large bundled entrypoint, and the targeted inspection did not resolve the reported account-setting behavior.
Source & flagged code
7 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.113.0.
See all versions of @feathery/react for other recorded verdicts.
- Review the evidence and your use of @feathery/react@2.113.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.