@agimon-ai/po-browse-tool@0.0.0-alpha.59
MCP server for browser automation using Playwright with profile management, page registry, and multi-browser support
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe scanner’s execution and environment signals match the package’s browser-launch and runtime configuration behavior. The manifest has no install hook, and inspected runtime paths and required dependency files show no concrete attack behavior.
Decision evidence
public snapshot- The manifest points to the inspected CommonJS and ESM runtime entrypoints and defines no install lifecycle hook.
- The runtime operation checks that a requested profile matches the bound runtime; its CommonJS and ESM builds contain the same check.
- The process launch code starts Chrome for browser automation, and the operation wrapper handles aborts and reports failures.
- The three inspected required dependencies expose registry, process-management, and validation utilities; their manifests show no install scripts.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @agimon-ai/po-browse-tool@0.0.0-alpha.59.
See all versions of @agimon-ai/po-browse-tool for other recorded verdicts.
- Review the evidence and your use of @agimon-ai/po-browse-tool@0.0.0-alpha.59 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.