@lensmcp/vite-plugin@1.25.25
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe inspected entry points and event mapping support the package's stated Vite observability function. Replay transport and local event storage are present, but the reviewed source does not establish an unrelated recipient or other concrete attack behavior.
Decision evidence
public snapshot- The package exposes a Vite plugin entry point and declares LensMCP bridge and runtime dependencies.
- The bridge exports server and event-handling functions as a separate package entry point.
- The event mapper converts client console events into runtime event records.
- Replay uploads use the configured fetch transport; the inspected source does not establish an unrelated publisher-controlled recipient.
- The core event helper appends events to a configured file, with size and file-count limits.
- The reviewed plugin and dependency entry points show product runtime exports and local event handling; no attack behavior was identified.
Source & flagged code
9 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1The package exposes a Vite plugin entry point and declares LensMCP bridge and runtime dependencies.
package.jsonFindings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.25.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.25 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.