@redhat-cloud-services/frontend-components-config@6.14.18
Config plugins and settings for RedHat Cloud Services project.
AI Security Review
scanned 21h ago · by lpm-firewall-aiThe scanner’s process and network indicators map to development tooling, while package.json has no install hooks. The inspected runtime behavior is tied to CLI and build use and does not establish malicious activity.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the fec CLI or requests a webpack build.
Impact
These actions support project development and build setup; the inspected paths do not establish covert collection, credential disclosure, persistence, or destructive behavior.
Mechanism
The CLI can add TypeScript build dependencies and a ts-patch postinstall step to the project manifest, and its build helper starts webpack for the selected config. The host-file edit is exposed as a separate named command.
AI rationale
The scanner’s process and network indicators map to development tooling, while package.json has no install hooks. The inspected runtime behavior is tied to CLI and build use and does not establish malicious activity.
Evidence
package.json
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no lifecycle scripts and declares the expected webpack config entrypoints.
- The build helper launches webpack for the requested project config when the build command is invoked.
- The fec CLI exposes host-file setup as a named command and performs TypeScript setup through project-specific tooling.
- The inspected dependency sources provide webpack refresh, config utilities, validation, logging, and style-search functionality.
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 · L17bin/webpack.plugins.js
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
LowSuspicious Dependency Evidence.lpm-dependency-evidence-a683301a-b53b-4ff2-8765-14f7ecb8d67d/0/npm-linux/package.json
Affected versions and remediation
This report applies to @redhat-cloud-services/frontend-components-config@6.14.18.
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.18 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.