@redhat-cloud-services/frontend-components-config@6.14.11
Config plugins and settings for RedHat Cloud Services project.
AI Security Review
scanned 23d ago · by lpm-firewall-aiInspected behavior is consistent with frontend build and development tooling activated by callers. No concrete credential exfiltration, malicious install chain, or AI-agent control mutation was found.
Static reason
One or more suspicious static signals were detected.
Trigger
Users invoke the fec CLI or call the exported configuration factory; no npm install lifecycle hook is declared.
Impact
Expected effects include build output, project build configuration updates, and development containers; no malicious impact was established.
Mechanism
The CLI runs build tools, prepares TypeScript dependencies, and starts development services. Inspected network operations retrieve development resources rather than export harvested credentials.
AI rationale
Inspected behavior is consistent with frontend build and development tooling activated by callers. No concrete credential exfiltration, malicious install chain, or AI-agent control mutation was found.
Evidence
package.jsontsconfig.json/etc/hosts
Network endpoints1
raw.githubusercontent.com/RedHatInsights/chrome-service-backend/main
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares no lifecycle scripts and no runtime self-dependency.
- bin/build-script.js launches webpack for an invoked production build.
- bin/fec.js checks and installs TypeScript build dependencies when the CLI runs.
- lib/index.js returns webpack configuration and plugins.
- The development interceptor fetches navigation data from the RedHatInsights repository without forwarding request credentials.
Evidence against
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flagged · loading sourcebin/build-script.jsView file
6var path_1 = require("path");
L7: var child_process_1 = require("child_process");
L8: function buildScript(argv, cwd) {
High
Child Process
Package source references child process execution.
bin/build-script.jsView on unpkg · L620cwd: cwd,
L21: shell: true,
L22: });
High
17process.env.NODE_ENV = 'production';
L18: var subprocess = (0, child_process_1.spawn)("npm exec -- webpack -c ".concat(configPath), [], {
L19: stdio: [process.stdout, process.stdout, process.stdout],
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
bin/build-script.jsView on unpkg · L1717
Findings
3 High4 Medium5 Low
HighChild Processbin/build-script.js
HighShellbin/build-script.js
HighRuntime Package Installbin/build-script.js
MediumDynamic Requirebin/webpack.plugins.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencebin/build-script.js
Affected versions and remediation
This report applies to @redhat-cloud-services/frontend-components-config@6.14.11.
See all versions of @redhat-cloud-services/frontend-components-config for other recorded verdicts.
- Review the evidence and your use of @redhat-cloud-services/frontend-components-config@6.14.11 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.