comein-player-web
Customer-facing Web SDK built on top of the Comein player SDK.
This report shows the evidence for comein-player-web@0.1.0. 1 of 24 known versions is blocked or flagged. The newest version, 0.2.3, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe UMD entrypoint is intentionally obfuscated and dynamically evaluates generated code. This is concrete opaque runtime execution in the package's normal import path.
Decision evidence
public snapshot- The default package entrypoint is the UMD bundle.
- The UMD bundle contains deliberately obfuscated control flow that dynamically evaluates a constructed string.
- The manifest has no install or lifecycle scripts.
- The visible ESM authentication code uses named Comein service endpoints, but it does not explain the opaque UMD evaluator.
Source & flagged code
5 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 · L1The UMD bundle contains deliberately obfuscated control flow that dynamically evaluates a constructed string.
dist/index.umd.jsView on unpkg · L77Findings
Affected versions and remediation
This report applies to comein-player-web@0.1.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing comein-player-web@0.1.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.