registry / @recallai/desktop-sdk / 2.0.36
@recallai/desktop-sdk@2.0.36
Recall Desktop SDK
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe install-time network and file operations implement package-local native SDK setup from Recall’s release host. The inspected runtime behavior is API-driven, and no concrete malicious behavior was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation runs setup.js; a consumer’s call to init starts the native process.
Impact
No confirmed attack surface was established in the inspected source.
Mechanism
The installer fetches a native archive from Recall’s release host and extracts it into package-local directories. The JavaScript API starts the bundled executable and sends it caller-provided configuration and commands.
AI rationale
The install-time network and file operations implement package-local native SDK setup from Recall’s release host. The inspected runtime behavior is API-driven, and no concrete malicious behavior was identified.
Evidence
setup.jspackage.jsonindex.jsFrameworksgstreamer-1.0
Network endpoints1
recallai-desktop-sdk-releases.s3.us-east-1.amazonaws.com
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs setup.js from its install hook.
- setup.js downloads platform-specific native SDK archives from Recall’s release host using the package commit identifier, then extracts them into the package.
- The installer removes only package-local Frameworks or gstreamer-1.0 directories before extraction.
- index.js starts the bundled native executable through init and passes it the caller’s SDK options.
- The inspected runtime-operation location only forwards a log command while the native process is active.
Evidence against
- The install hook performs a remote download and replaces package-local native files; the inspected source ties this to platform SDK setup.
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":
Low
Suspicious Lifecycle Evidence
package.json runs setup.js from its install hook.
package.jsonView on unpkg · L14index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @recallai/desktop-sdk@2.0.39
matchedIdentity = npm:QHJlY2FsbGFpL2Rlc2t0b3Atc2Rr:2.0.39
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
High
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
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.36.
See all versions of @recallai/desktop-sdk for other recorded verdicts.
- Review the evidence and your use of @recallai/desktop-sdk@2.0.36 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.