comein-player-web@0.1.8
Customer-facing Web SDK built on top of the Comein player SDK.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has no install-time behavior, but its runtime logger explicitly places authentication tokens in telemetry data. That is a real unresolved credential-handling risk, though the inspected source does not establish malicious intent.
Decision evidence
public snapshot- The browser logger includes the supplied user token or web token in its default telemetry payload along with identifying and browser data.
- Importing the package selects a browser bundle as its main and module entry point.
- The manifest has no install or lifecycle scripts.
- The inspected behavior is a customer-facing web player, storage, authentication, and telemetry code; no Node command execution or project-file mutation was found.
- The stylesheet is ordinary UI and font styling.
Source & flagged code
4 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 browser logger includes the supplied user token or web token in its default telemetry payload along with identifying and browser data.
dist/index.umd.jsView on unpkg · L52Findings
Affected versions and remediation
This report applies to comein-player-web@0.1.8.
See all versions of comein-player-web for other recorded verdicts.
- Review the evidence and your use of comein-player-web@0.1.8 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.