@lensmcp/vite-plugin@1.25.47
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe entry point exports a Vite plugin, and the inspected runtime behavior is centered on serving an authenticated local event bridge and collecting browser observability data. The environment-variable references control build or watch behavior, with no evidence they are collected or sent to an unrelated host.
Decision evidence
public snapshot- The package metadata identifies it as a Vite plugin and exposes index.js as its entry point; it declares no lifecycle scripts.
- The plugin starts its bridge when Vite configures a development server, using 127.0.0.1 by default and a generated token; it instruments browser events for that bridge.
- Environment variables are used for build settings and optional extra watch roots; no automatic collection or transmission of their values was identified.
Source & flagged code
6 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.47.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.47 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.