@salesforce/b2c-cli@2.10.2
A Salesforce B2C Commerce CLI
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package configures runtime telemetry to an Azure Application Insights endpoint, and its development launcher explicitly describes command events while the normal launcher lacks equivalent disclosure or opt-in behavior. This is a telemetry transparency concern; the inspected source does not establish a harmful payload or credential exfiltration.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI through its normal launcher.
Impact
Runtime usage data may be sent to the configured telemetry service; the exact payload is not established by the inspected package source.
Mechanism
The package manifest supplies an Application Insights connection string. The development launcher identifies command start and success events and disables telemetry by default, but the normal launcher does not show a comparable disclosure or opt-in.
AI rationale
The package configures runtime telemetry to an Azure Application Insights endpoint, and its development launcher explicitly describes command events while the normal launcher lacks equivalent disclosure or opt-in behavior. This is a telemetry transparency concern; the inspected source does not establish a harmful payload or credential exfiltration.
Evidence
package.jsonbin/run.jsbin/dev.js
Network endpoints2
eastus-8.in.applicationinsights.azure.comeastus.livediagnostics.monitor.azure.com
Decision evidence
public snapshotAI called this Suspicious at 78.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json configures Oclif telemetry with an Azure Application Insights connection string.
- The normal CLI launcher invokes Oclif; this package does not show a production telemetry opt-in or disclosure.
- The development launcher disables telemetry by default and says setting SFCC_DISABLE_TELEMETRY=false or SF_DISABLE_TELEMETRY=false enables COMMAND_START/COMMAND_SUCCESS events.
Evidence against
- The flagged secret strings in the hidden test command are dummy values passed to a logger redaction test.
- The AWS credential example is documentation showing placeholder names and an S3 endpoint.
- No install lifecycle scripts or unrelated credential-exfiltration flow were identified.
Behavioral surface
CryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/commands/_test/index.jsView file
30patternName = generic_password
severity = medium
line = 30
Medium
Secret Pattern
Package contains a possible secret pattern.
dist/commands/_test/index.jsView on unpkg · L30bin/dev.cmdView file
•path = bin/dev.cmd
kind = build_helper
sizeBytes = 193
magicHex = [redacted]
Medium
package.jsonView file
80"oclif": {
"bin": "b2c",
"dirname": "b2c",
"commands": "./dist/commands",
"helpClass": "./dist/help",
"telemetry": {
"connectionString": "InstrumentationKey=6fcc215f-0b11-4864-ad5c-3945ae19e2f3;IngestionEndpoint=https://eastus-8.in.applicationinsights.azure.com/;LiveEndpoint=https://eastus.l
Findings
8 Medium4 Low
MediumSecret Patterndist/commands/_test/index.js
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperbin/dev.cmd
MediumStructural Risk Force Deep Review
MediumAi Review Evidencepackage.json
MediumAi Review Evidencebin/run.js
MediumAi Review Evidencebin/dev.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @salesforce/b2c-cli@2.10.2.
See all versions of @salesforce/b2c-cli for other recorded verdicts.
- Review the evidence and your use of @salesforce/b2c-cli@2.10.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.