@lensmcp/vite-plugin@1.24.0
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 25d ago · by lpm-firewall-aiSource inspection found ordinary Vite plugin behavior and package-aligned LensMCP dependencies, with no concrete attack behavior. The static hints do not establish maliciousness.
Decision evidence
public snapshot- package.json exposes the Vite plugin through index.js and lists matching LensMCP bridge and instrumentation dependencies.
- lib/plugin.js activates as a Vite plugin for serving, with build activation gated by an option or environment setting.
- lib/plugin.js starts the bridge during Vite server configuration, using a loopback host by default and a generated token.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1lib/plugin.js activates as a Vite plugin for serving, with build activation gated by an option or environment setting.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.24.0.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.24.0 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.