tdem-electron-sdk@0.4.2
tdem sdk for electron applications
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has a real data-exfiltration surface for filesystem metadata after explicit SDK initialization, but the source does not establish malicious installation behavior or covert payload execution. Warn so consumers can assess telemetry consent and collector configuration.
Decision evidence
public snapshot- The main bundle defines a default telemetry collector and uses Electron networking to send requests.
- The main bundle records filesystem operation metadata, including file paths.
- The renderer bundle records filesystem operation metadata, including file paths.
- package.json has no preinstall, install, postinstall, or other automatic lifecycle hook.
- The observed behavior is activated by the Electron SDK initialization path, not package installation or import alone.
- Source inspection found no command execution, credential harvesting, or destructive action.
Source & flagged code
6 flaggedBrowser source reuses an authenticated session to collect identity data and mutate account settings while reporting externally.
lib/tdemelectron-renderer.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to tdem-electron-sdk@0.4.2.
See all versions of tdem-electron-sdk for other recorded verdicts.
- Review the evidence and your use of tdem-electron-sdk@0.4.2 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.