@lensmcp/vite-plugin@1.25.32
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package starts a token-protected bridge as part of Vite server configuration, defaulting to 127.0.0.1, and replay behavior follows local settings or explicit configuration. The reviewed sources show no install-time contact, credential exfiltration, or unrelated external destination.
Decision evidence
public snapshot- The package entry exports the Vite plugin from its own index.js module.
- The bridge is created during Vite server configuration and receives the plugin's configured host, a generated token, and optional allowed origins.
- The bridge's default host is 127.0.0.1; its host and port can be configured through environment variables.
- Replay behavior is controlled by LENSMCP_REPLAY, the plugin option, or the local capture settings.
- Replay uploads use the configured endpoint and omit browser credentials.
- The plugin injects browser instrumentation and can capture application events, including session replay when enabled by its settings.
- The host can be overridden, so a user configuration can direct the bridge away from loopback.
Source & flagged code
6 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1The bridge is created during Vite server configuration and receives the plugin's configured host, a generated token, and optional allowed origins.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.32.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.32 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.