registry / @recallai/desktop-sdk / 2.0.39
@recallai/desktop-sdk@2.0.39
Recall Desktop SDK
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe install and network signals resolve to native SDK setup using the package's commit identifier and Recall's release bucket. The flagged runtime operation sends logs to the active local SDK subprocess; the inspected JavaScript does not establish a malicious transfer or mutation.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs setup.js; runtime logging occurs while the SDK process is active.
Impact
The setup installs package components. The inspected JavaScript does not show the flagged log operation sending data to an external recipient.
Mechanism
The installer fetches a commit-selected native archive from the Recall release bucket. The runtime log operation queues a command to the local subprocess.
AI rationale
The install and network signals resolve to native SDK setup using the package's commit identifier and Recall's release bucket. The flagged runtime operation sends logs to the active local SDK subprocess; the inspected JavaScript does not establish a malicious transfer or mutation.
Evidence
desktop_sdk_macos.tardesktop_sdk_win32.tarFrameworks/gstreamer-1.0/
Network endpoints1
recallai-desktop-sdk-releases.s3.us-east-1.amazonaws.com
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest's install hook runs setup.js during package installation.
- setup.js reads the package's commit identifier to select a native SDK release.
- The setup downloads archives from the package's Recall release bucket into package-local files.
- The flagged runtime log operation sends a log command only while the native SDK process is active.
- The command is queued to the native process's stdin; init is an exported SDK API.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
4 flaggedpackage.jsonView file
•scripts.install = node ./setup.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg15"install": "node ./setup.js",
"valid
Low
Suspicious Lifecycle Evidence
The manifest's install hook runs setup.js during package installation.
package.jsonView on unpkg · L15setup.jsView file
76async function setup() {
const package = fs.readFileSync("./package.json");
const packageJson = JSON.parse(package);
const commit_sha = packageJson["commit_sha"];
console.log(`Downloading native sdk for id: ${commit_sha}, platform: ${process.platform}`);
if (process.platform === "darwin") {
await se
Low
Ai Review Evidence
setup.js reads the package's commit identifier to select a native SDK release.
Findings
1 High3 Medium8 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencesetup.js
LowAi Review Evidencesetup.js
Affected versions and remediation
This report applies to @recallai/desktop-sdk@2.0.39.
See all versions of @recallai/desktop-sdk for other recorded verdicts.
- Review the evidence and your use of @recallai/desktop-sdk@2.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.