@cursor/sdk@1.0.39
⚠ Under reviewTypeScript SDK for Cursor agents.
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe inspected credential and PR attribution flows appear consistent with the SDK’s configured Cursor service and do not establish an attack. Because substantial bundled runtime code remains unresolved, a clean verdict is not supported by this review.
Decision evidence
public snapshot- The manifest routes package imports to CJS, ESM, or bundled runtime files and shows no install lifecycle hook.
- The CJS client reads a saved API key only when its stored backend matches the configured Cursor backend.
- The API client sends its key to its configured backend; the inspected default is a Cursor API host.
- The PR attribution path runs Git and forge queries, parses pull request metadata, and reports it through the SDK telemetry path.
- The inspected runtime excerpts do not establish credential theft or command-output exfiltration.
- Large bundled and chunked runtime files remain only partially reviewed, so the full behavior behind the flagged findings is unresolved.
Source & flagged code
15 flaggedSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/esm/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @cursor/sdk@1.0.39.
See all versions of @cursor/sdk for other recorded verdicts.
- Review the evidence and your use of @cursor/sdk@1.0.39 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.