@salesforce/b2c-cli@2.5.1
A Salesforce B2C Commerce CLI
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe inspected entrypoints start the CLI, and the credential transfer occurs within an explicit OAuth login flow to its configured Account Manager host. The scanner's secret-pattern finding is explained by sample values in a logger redaction test.
Decision evidence
public snapshot- The manifest identifies a Salesforce Commerce CLI and maps its `b2c` command to `bin/run.js`; its inspected scripts contain no registry-install hook.
- The launcher preloads environment configuration and starts the CLI framework.
- The OAuth command accepts an Account Manager host from configuration and builds an access-token URL from that host.
- The command sends its OAuth form body to that configured URL when the user invokes authentication.
- The secret-looking strings in the test command are sample values passed to a logger redaction check.
Source & flagged code
5 flaggedPackage contains a possible secret pattern.
dist/commands/_test/index.jsView on unpkg · L30Findings
Affected versions and remediation
This report applies to @salesforce/b2c-cli@2.5.1.
See all versions of @salesforce/b2c-cli for other recorded verdicts.
- Review the evidence and your use of @salesforce/b2c-cli@2.5.1 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.