@sortlist/cli@0.51.0
Sortlist platform CLI — GraphQL federation client
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package’s authentication flow appears directed to its configured Sortlist service, but the published CLI also sends runtime error context, including a configured endpoint, to Sentry without an evident opt-out. This is undisclosed identifying telemetry, so the package is suspicious rather than malicious.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the published CLI; endpoint and operation context are attached during GraphQL requests, and errors trigger reporting.
Impact
May disclose a private or internal API hostname and the operation being attempted to the package vendor’s telemetry service.
Mechanism
Sentry captures exceptions with endpoint and operation details, then the CLI flushes events to its fixed Sentry collector.
AI rationale
The package’s authentication flow appears directed to its configured Sortlist service, but the published CLI also sends runtime error context, including a configured endpoint, to Sentry without an evident opt-out. This is undisclosed identifying telemetry, so the package is suspicious rather than malicious.
Evidence
dist/index.js
Network endpoints1
o27611.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The published build initializes Sentry with a fixed collector; only local development skips initialization.
- Network errors are reported to Sentry with the configured API endpoint and operation name as context.
- The CLI captures command exceptions and flushes Sentry after command handling.
- Client credentials are posted to the configured token endpoint for Sortlist authentication.
Evidence against
- The package presents itself as a Sortlist platform CLI, and its GraphQL and OAuth requests use Sortlist endpoints by default.
- The Sentry code reports errors rather than showing automatic collection of credentials or file contents.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
4 flaggedbin/sl.mjsView file
1#!/usr/bin/env node
L2: import { execFileSync } from 'node:child_process';
L3: import { existsSync, readFileSync } from 'node:fs';
High
1Cross-file remote execution chain: bin/sl.mjs spawns dist/index.js; helper contains network access plus dynamic code execution.
L1: #!/usr/bin/env node
L2: import { execFileSync } from 'node:child_process';
L3: import { existsSync, readFileSync } from 'node:fs';
...
L6:
L7: const __dirname = dirname(fileURLToPath(import.meta.url));
L8: const selfRoot = resolve(__dirname, '..');
...
L11: * Walk upward from `start` looking for a @sortlist/cli checkout
L12: * (package.json with name === "@sortlist/cli" and no .published sentinel).
L13: * Returns the package root, or null.
...
L20: try {
L21: const pkg = JSON.parse(readFileSync(pkgPath, 'utf-8'));
L22: if (pkg.name === '@sortlist/cli' && !existsSync(resolve(dir, '.published'))) {
High
Cross File Remote Execution Context
Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
bin/sl.mjsView on unpkg · L1dist/index.jsView file
Findings
1 Critical2 High3 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/index.js
HighChild Processbin/sl.mjs
HighCross File Remote Execution Contextbin/sl.mjs
MediumNetwork
MediumEnvironment Vars
MediumAi Review Evidencedist/index.js
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @sortlist/cli@0.51.0.
See all versions of @sortlist/cli for other recorded verdicts.
- Review the evidence and your use of @sortlist/cli@0.51.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.