@getbrevo/cli@2.6.0
Brevo Developer CLI — create, manage apps and OAuth integrations
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged process execution belongs to agent CLI registration, while the inspected credential flows target Brevo API or OAuth services. The manifest’s lifecycle scripts are for development and publishing, with no install-time attack identified.
Decision evidence
public snapshot- The manifest identifies this as Brevo’s CLI, with its main entry and executable at dist/bin/index.js.
- API requests use the configured Brevo API base and attach the credential as an authentication header.
- OAuth refresh sends the refresh token to the configured Brevo OAuth proxy endpoint.
- The flagged child-process code runs an agent CLI without a shell and captures its output for local result handling.
- API-key login validates the key through the account service before saving credentials.
- The package has no install or postinstall hook; prepare and prepublishOnly are development and publishing scripts.
- The inspected startup path fetches CLI information and proceeds to command parsing; no unrelated collector or credential redirect was identified.
Source & flagged code
7 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/bin/index.jsView on unpkgPackage source references child process execution.
dist/bin/index.jsView on unpkg · L177Findings
Affected versions and remediation
This report applies to @getbrevo/cli@2.6.0.
See all versions of @getbrevo/cli for other recorded verdicts.
- Review the evidence and your use of @getbrevo/cli@2.6.0 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.