@contrail/cli@3.5.4
VibeIQ's Contrail Platform CLI.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo malicious install hook or covert automatic execution was found. The explicit deployment flow nevertheless packages sensitive local metadata and source for upload, while opaque bundled artifacts preclude a clean decision.
Static reason
One or more suspicious static signals were detected.
Trigger
Running contrail app publish or another app deployment command.
Impact
A publish operation can disclose project source and local host or Git metadata to the configured deployment service.
Mechanism
Collects local metadata, installs project dependencies, archives project files, and uploads the archive to a signed URL.
AI rationale
No malicious install hook or covert automatic execution was found. The explicit deployment flow nevertheless packages sensitive local metadata and source for upload, while opaque bundled artifacts preclude a clean decision.
Evidence
dist/helpers/app/metadata-extractor.jsdist/helpers/app/app-deployer.jspackage.jsonpackage-lock.jsonsrc/app.ymltmp/tmp/build-info.jsontmp/source-code.ziptmp.zip
Network endpoints1
api.vibeiq.com/prod/api
Decision evidence
public snapshotAI called this Suspicious at 79.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The publish path collects hostname, home directory, working directory, and Git metadata into build-info.json.
- Publishing runs npm install in a project temp directory, then packages and uploads the resulting archive.
- The release ships opaque compressed test/dependency artifacts that cannot safely support a clean source-grounded verdict.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- The risky behavior is reached by the explicit app publish command, not package installation.
- The inspected login endpoint is a fixed Contrail/VibeIQ API endpoint.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
12 flaggeddist/helpers/app/metadata-extractor.jsView file
5const os = tslib_1.__importStar(require("os"));
L6: const child_process_1 = require("child_process");
L7: const fs_1 = tslib_1.__importDefault(require("fs"));
High
Child Process
Package source references child process execution.
dist/helpers/app/metadata-extractor.jsView on unpkg · L5node_modules/@opentelemetry/otlp-transformer/node_modules/@opentelemetry/resources/build/esm/detectors/platform/node/machine-id/execAsync.jsView file
17import * as util from 'util';
L18: export const execAsync = util.promisify(child_process.exec);
L19: //# sourceMappingURL=execAsync.js.map
High
Shell
Package source references shell execution.
node_modules/@opentelemetry/otlp-transformer/node_modules/@opentelemetry/resources/build/esm/detectors/platform/node/machine-id/execAsync.jsFindings
7 High7 Medium6 Low
HighChild Processdist/helpers/app/metadata-extractor.js
HighShellnode_modules/@opentelemetry/otlp-transformer/node_modules/@opentelemetry/resources/build/esm/detectors/platform/node/machine-id/execAsync.js
HighObfuscated Payload Loadernode_modules/protobufjs/dist/protobuf.js
HighRuntime Package Installdist/helpers/app/app-deployer.js
HighShips High Entropy Blobnode_modules/amazon-cognito-identity-js/dist/amazon-cognito-identity.min.js.gz
HighPayload In Excluded Dirnode_modules/thread-stream/test/dir with spaces/test-package.zip
HighSemantic Analysis Limitednode_modules/@contrail/telemetry/lib/logger/index.js#virtual:normalized:round1
MediumDynamic Requiredist/logger.js
MediumUnsafe Vm Contextnode_modules/pino/benchmarks/utils/wrap-log-level.js
Affected versions and remediation
This report applies to @contrail/cli@3.5.4.
See all versions of @contrail/cli for other recorded verdicts.
- Review the evidence and your use of @contrail/cli@3.5.4 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.