@lensmcp/vite-plugin@1.25.24
⚠ Under reviewLensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe visible source shows normal Vite plugin activation and no install hook, but the active entrypoint imports the unavailable bridge package and plugin code starts its server. Review those runtime dependencies before reaching a clean or malicious verdict.
Decision evidence
public snapshot- The package entrypoint loads the plugin and imports the bridge package.
- The Vite server hook starts a bridge server and serves a generated browser client runtime.
- The bridge and client runtime are declared runtime dependencies, but their source was unavailable for inspection.
- The manifest declares no lifecycle scripts; the plugin activates through Vite's serve command, with build activation disabled by default.
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 package entrypoint loads the plugin and imports the bridge package.
lib/plugin.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.24.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Review the evidence and your use of @lensmcp/vite-plugin@1.25.24 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.