@sojogg/sdk@0.1.5
Sojo: one account, every game. The browser client and the server helpers for games on Sojo.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest exposes ordinary client and server entrypoints, while the browser client defaults to Sojo’s identity service and performs no work on import. Its observed tracking and optional legacy-token forwarding use the configured Sojo frame; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json exposes client and server runtime entrypoints.
- The client defaults to Sojo’s identity origin and mounts its frame only after init() is called.
- The client sends messages to its frame at the configured origin and rejects messages from other windows or origins.
- Initialization queues a page-load event with a shortened referrer for delivery through the Sojo frame.
- A legacy token is forwarded only when supplied through the caller’s legacy option; the documented custom origin is for a local Sojo instance.
Source & flagged code
9 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/core.js#virtual:normalized:round1View on unpkgpackage.json exposes client and server runtime entrypoints.
package.jsonView on unpkg · L8Findings
Affected versions and remediation
This report applies to @sojogg/sdk@0.1.5.
See all versions of @sojogg/sdk for other recorded verdicts.
- Review the evidence and your use of @sojogg/sdk@0.1.5 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.