registry / @feathery/react / 2.115.2
@feathery/react@2.115.2
React library for Feathery
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe suspicious signals resolve to ordinary Feathery SDK networking, optional analytics integrations, and Base64 validation/JWT parsing. The main entry exports an initialization API rather than automatically performing the flagged account or analytics actions on import.
Static reason
One or more suspicious static signals were detected.
Trigger
Consumers explicitly call the exported init API; analytics integrations run when supplied by the form configuration.
Impact
Expected form and configured analytics traffic; no evidence of unrelated credential collection or unrequested account actions.
Mechanism
The SDK communicates with Feathery API endpoints and, when configured, analytics providers. Segment user identification requires identify_user to be enabled.
AI rationale
The suspicious signals resolve to ordinary Feathery SDK networking, optional analytics integrations, and Base64 validation/JWT parsing. The main entry exports an initialization API rather than automatically performing the flagged account or analytics actions on import.
Network endpoints7
api.feathery.ioapi-au.feathery.ioapi-eu.feathery.ioapi-ca.feathery.ioapi-jp.feathery.iostaging.feathery.iocdn.rudderlabs.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Package entry points load the Feathery library; init is a public API that requires an SDK key.
- The runtime installs Segment only when an integrations.segment configuration is present and loads it with that configuration's API key.
- Segment user identification is conditional on identify_user being enabled.
- The package's declared prepare script runs husky; prepublishOnly runs the package build.
Evidence against
- The package includes analytics integrations that can transmit form metadata and submitted fields when configured.
- The SDK can update a user's Feathery identity through its service API.
Behavioral surface
DynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationTelemetryUrlStrings
Source & flagged code
6 flaggedumd/index.jsView file
1/*! For license information please see index.js.LICENSE.txt */
L2: !function(e,t){"object"==typeof exports&&"object"==typeof module?module.exports=t():"function"==typeof define&&define.amd?define([],t):"object"==typeof exports?exports.Feathery=t()...
High
Browser Session Account Hijack
Browser source reuses an authenticated session to collect identity data and mutate account settings while reporting externally.
umd/index.jsView on unpkg · L11/*! For license information please see index.js.LICENSE.txt */
L2: !function(e,t){"object"==typeof exports&&"object"==typeof module?module.exports=t():"function"==typeof define&&define.amd?define([],t):"object"==typeof exports?exports.Feathery=t()...
Low
Eval
Package source references a known benign dynamic code generation pattern.
umd/index.jsView on unpkg · L1dist/fthry_index.8xCAXFhd.jsView file
3657try {
L3658: var util = require('util');
L3659: /* istanbul ignore next */
Findings
3 High5 Medium7 Low
HighBrowser Session Account Hijackumd/index.js
HighBase64 Obscured Urlcjs/fthry_index.6oGSpCIA.js
HighSemantic Analysis Limitedcjs/fthry_index.6oGSpCIA.js
MediumDynamic Requiredist/fthry_index.8xCAXFhd.js
MediumNetwork
MediumEnvironment Vars
MediumOversized Source Filedist/fthry_index.hMOczhH3.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvalumd/index.js
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
Affected versions and remediation
This report applies to @feathery/react@2.115.2.
See all versions of @feathery/react for other recorded verdicts.
- Review the evidence and your use of @feathery/react@2.115.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.