@oked/cursor@0.6.25
OKed for Cursor. A preToolUse hook that holds risky agent tool calls for a human decision.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package’s intended approval flow is consistent with its purpose, and no harmful install-time behavior was identified. However, the automatically triggered heartbeat sends the machine hostname to the vendor backend without disclosed consent, which meets the suspicious telemetry criteria.
Decision evidence
public snapshot- The hook-core decision path calls the heartbeat before its safe-action fast path, so paired installs can send it during ordinary tool use; it is throttled to once a day by default.
- The SDK posts the machine hostname to the configured backend’s heartbeat endpoint using the paired API key.
- The package manifest has no install, preinstall, or postinstall script; its only lifecycle script is prepublishOnly.
- The heartbeat requires an API key and goes to the configured OKed backend, consistent with the package’s approval service.
- The Cursor hook configuration is written by the explicit `oked-cursor init` command, not automatically during installation.
Source & flagged code
4 flaggedThe hook-core decision path calls the heartbeat before its safe-action fast path, so paired installs can send it during ordinary tool use; it is throttled to once a day by default.
.lpm-dependency-evidence-60de6a2d-bbe9-4028-aa05-d7e1d9f6d7ca/0/npm-linux/dist/decide.jsView on unpkg · L62Findings
Affected versions and remediation
This report applies to @oked/cursor@0.6.25.
See all versions of @oked/cursor for other recorded verdicts.
- Review the evidence and your use of @oked/cursor@0.6.25 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.