comein-player-web@0.1.10
Customer-facing Web SDK built on top of the Comein player SDK.
AI Security Review
scanned 23d ago · by lpm-firewall-aiInspected entrypoints and authentication behavior are consistent with the package's browser player functionality. Dynamic execution and telemetry did not establish a concrete malicious chain.
Decision evidence
public snapshot- package.json exposes browser SDK bundles and contains no lifecycle scripts or runtime dependencies.
- Player creation explicitly authenticates information supplied by the caller.
- Both bundles use caller-supplied user information for authentication and browser session storage.
- The stylesheet loads local icon fonts and contains no HTTP references.
- Bundled telemetry uses a fixed Comein logging project.
- The bundle contains obfuscated developer-tools detection and dynamic execution, but inspection linked these to player debugging protection and media processing rather than an attack.
Source & flagged code
6 flagged · loading sourceBrowser source reuses an authenticated session to collect identity data and mutate account settings while reporting externally.
dist/index.umd.jsView on unpkg · L1Player creation explicitly authenticates information supplied by the caller.
dist/index.umd.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to comein-player-web@0.1.10.
See all versions of comein-player-web for other recorded verdicts.
- Review the evidence and your use of comein-player-web@0.1.10 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.