@lensmcp/vite-plugin@1.25.44
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe plugin enables browser replay by default, and the recorder config explicitly leaves password values unmasked before uploading replay data. This automatically collects credentials that the observability purpose does not need, so the package should be blocked.
Decision evidence
public snapshot- Replay defaults to enabled when no capture setting is present.
- When replay is enabled, the Vite plugin injects its replay module into served pages.
- The recorder’s defaults disable masking of all inputs and explicitly set password masking to false.
- The plugin configures replay to use its bridge host and port; the default host is 127.0.0.1.
- The replay uploader POSTs replay data and blobs to the bridge’s /replay and /replay/blob paths.
- The package is intended to provide browser observability, and its replay upload destination defaults to a local bridge.
- The manifest has no lifecycle scripts; replay runs when the configured Vite development server serves a page.
Source & flagged code
9 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1Source fingerprint signature matches a known malicious package signature; route for source-aware review.
lib/plugin.jsView on unpkgFindings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.44.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Avoid installing @lensmcp/vite-plugin@1.25.44. 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.