@sortlist/cli@0.48.0
Sortlist platform CLI — GraphQL federation client
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe source initializes Sentry for published CLI runs and sends captured exceptions without an evident opt-out or disclosure in the inspected code. The credential flow itself posts Sortlist client credentials to the configured token endpoint, so the finding is telemetry rather than credential exfiltration.
Decision evidence
public snapshot- The CLI initializes Sentry outside local development and sends exception events to a fixed Sentry DSN.
- Captured errors can include the GraphQL operation name and endpoint; command errors are captured and flushed during CLI startup.
- Sortlist client credentials are posted to the configured token endpoint, rather than being sent through the Sentry error-reporting path.
- The credential exchange uses the configured token endpoint for the Sortlist CLI’s client-credentials flow.
- The launcher invokes the bundled CLI when the user runs the command; the inspected entry code shows no install-time credential collection.
Source & flagged code
4 flaggedSource spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
bin/sl.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @sortlist/cli@0.48.0.
See all versions of @sortlist/cli for other recorded verdicts.
- Review the evidence and your use of @sortlist/cli@0.48.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.