registry / @recallai/desktop-sdk / 2.0.38
@recallai/desktop-sdk@2.0.38
Recall Desktop SDK
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe install-time download and native process launch match the package’s desktop SDK function: the source selects platform archives from Recall’s release host and starts the local process through initialization. I found no concrete unrelated data transfer or malicious behavior in the inspected source.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation downloads platform components; an application calling init starts the native SDK process.
Impact
No unrelated collection, credential transfer, or consumer-system mutation was established from the inspected source.
Mechanism
The installer fetches a platform archive from Recall’s release host and extracts it into the package directory. Runtime logs are passed to the active native process through the SDK command channel.
AI rationale
The install-time download and native process launch match the package’s desktop SDK function: the source selects platform archives from Recall’s release host and starts the local process through initialization. I found no concrete unrelated data transfer or malicious behavior in the inspected source.
Evidence
package.jsonsetup.jsindex.js
Network endpoints2
recallai-desktop-sdk-releases.s3.us-east-1.amazonaws.comapi.recall.ai
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- package.json defines an install hook that runs setup.js.
- setup.js chooses a macOS or Windows native SDK archive using the package commit identifier; the archive host is Recall’s release bucket.
- setup.js extracts the archive into the package directory, replacing the platform SDK files it manages.
- The runtime logging operation formats log data and sends it through the SDK command channel only when the native process is running.
- The SDK’s initialization path starts the native process, and its default API endpoint is Recall’s HTTPS 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 unpkg14"scripts": {
"install": "node ./setup.js",
"validate-types": "tsc --noEmit",
"build": "tsc -p tsconfig.build.json"
},
"devDependencies": {
"@types/node":
Low
Suspicious Lifecycle Evidence
package.json defines an install hook that runs setup.js.
package.jsonView on unpkg · L14index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @recallai/desktop-sdk@2.0.37
matchedIdentity = npm:QHJlY2FsbGFpL2Rlc2t0b3Atc2Rr:2.0.37
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
High
Previous Version Dangerous Delta
Findings
2 High3 Medium7 Low
HighInstall Time Lifecycle Scriptspackage.json
HighPrevious Version Dangerous Deltaindex.js
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
Affected versions and remediation
This report applies to @recallai/desktop-sdk@2.0.38.
See all versions of @recallai/desktop-sdk for other recorded verdicts.
- Review the evidence and your use of @recallai/desktop-sdk@2.0.38 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.