@lensmcp/vite-plugin@1.25.56
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 11h ago · by lpm-firewall-aiThe source matches a Vite observability plugin: it exposes the plugin through the package entry point and activates it during Vite serving. Replay can involve browser page data, but the inspected flow supports the package’s observability feature and shows no unrelated destination or secret collection.
Decision evidence
public snapshot- The manifest exports a Vite plugin and declares no lifecycle scripts.
- The plugin is applied to Vite serve by default; replay can be controlled through plugin settings and LENSMCP_REPLAY.
- The bridge and browser runtime support collecting and forwarding diagnostic events for the package’s observability purpose.
- Replay may be enabled by default when no capture setting disables it, so browser page data can be recorded during development.
- No unrelated collector, credential collection, install-time behavior, or harmful action was identified.
Source & flagged code
4 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1The plugin is applied to Vite serve by default; replay can be controlled through plugin settings and LENSMCP_REPLAY.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.56.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.56 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.