@cursor/sdk@1.0.35
TypeScript SDK for Cursor agents.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspection of all required locations and the authentication callers supports ordinary SDK credential handling and workspace parsing. No concrete malicious behavior or unresolved warning-level capability was established.
Decision evidence
public snapshot- package.json declares SDK entrypoints without automatic install hooks or a runtime self-dependency.
- The flagged bundled, CommonJS and ES module locations select .cursor/sdk/auth.json for SDK authentication storage; inspected saves restrict filesystem permissions.
- Both flagged 689.js locations parse workspace paths without writing agent configuration; the inspected caller handles missing terminal directories.
- Saved SDK credentials are reused only when unexpired and their backend matches the selected backend.
- The explicit Cursor.auth.login caller obtains a new API key from the selected backend and optionally saves it with that backend recorded.
Source & flagged code
15 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/esm/index.jsView on unpkg · L1Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/esm/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @cursor/sdk@1.0.35.
See all versions of @cursor/sdk for other recorded verdicts.
- Review the evidence and your use of @cursor/sdk@1.0.35 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.