@lensmcp/vite-plugin@1.25.46
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package has no install scripts, and its entry point only exports plugin functions. Runtime instrumentation is activated when Vite configures the plugin and connects to a bridge that defaults to loopback, consistent with the package's stated purpose.
Decision evidence
public snapshot- Package metadata exposes index.js and lists dependencies but defines no install lifecycle scripts.
- The entry point exports the Vite plugin and event handler; it does not invoke them on import.
- The plugin applies to Vite serve mode by default, starts its bridge during configureServer, and gates build use behind an option or environment variable.
- The bridge defaults to 127.0.0.1 and listens on the configured host and port.
- When enabled in Vite, the plugin instruments application code and sends runtime events through a browser client; this is consistent with its stated observability purpose.
Source & flagged code
7 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.46.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.46 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.