registry / @flashcatcloud/electron-sdk / 0.3.0
@flashcatcloud/electron-sdk@0.3.0
FlashCat SDK for Electron applications
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe inspected entry points and transport implement the package’s stated Electron RUM monitoring purpose, with uploads directed to the configured intake. The separate dd-trace instrumentation telemetry is disabled by default, while explicit application settings are preserved.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The host application imports the documented instrumentation entry point and initializes or uses the SDK.
Impact
Monitoring data and processed crash reports are delivered to the configured intake as part of the package’s stated function.
Mechanism
dd-trace instruments Electron and network activity; the SDK batches RUM events and uploads them to the configured site or proxy. Crash dumps are processed as monitoring events.
AI rationale
The inspected entry points and transport implement the package’s stated Electron RUM monitoring purpose, with uploads directed to the configured intake. The separate dd-trace instrumentation telemetry is disabled by default, while explicit application settings are preserved.
Evidence
Electron userData directory for SDK state and event batchesElectron crashDumps directory (read)
Network endpoints2
127.0.0.1:8126 (dd-trace telemetry endpoint, disabled by default)Configured site or proxy, using /api/v2/rum
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The README describes an Electron RUM SDK and documents importing its instrumentation entry point before Electron.
- The manifest declares dd-trace as a runtime dependency and Electron as a peer dependency.
- The instrumentation entry initializes dd-trace for Electron monitoring when explicitly imported.
- Instrumentation telemetry to Datadog is disabled by default, and the code preserves an explicit host-application setting.
- The SDK builds its RUM upload URL from the configured site or proxy and uses the /api/v2/rum track.
- Crash dumps are read from Electron’s crashDumps directory for processing as monitoring events.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicense
Source & flagged code
3 flaggeddist/instrument.cjs#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 3
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/instrument.cjs#virtual:normalized:round1View on unpkgpackage.jsonView file
•devDependencies changed=json-schema-to-typescript
Critical
Manifest Confusion
Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkgdist/instrument.cjsView file
Findings
1 Critical2 High3 Medium6 Low
CriticalManifest Confusionpackage.json
HighSemantic Analysis Limiteddist/instrument.cjs#virtual:normalized:round1
HighPrevious Version Dangerous Deltadist/instrument.cjs
MediumNetwork
MediumEnvironment Vars
MediumGit Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @flashcatcloud/electron-sdk@0.3.0.
See all versions of @flashcatcloud/electron-sdk for other recorded verdicts.
- Review the evidence and your use of @flashcatcloud/electron-sdk@0.3.0 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.