@agimon-ai/po-browse-tool@0.30.14-alpha.2
MCP server for browser automation using Playwright with profile management, page registry, and multi-browser support
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe package manifest has no install-time hook, and the inspected execution and network code aligns with browser automation and browser setup. Scanner signals alone do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines no lifecycle hook; its scripts are development and build tasks.
- Both runtime entrypoints expose browser APIs that check the bound profile before launching a browser.
- The Chrome setup code obtains version data and downloads the selected browser executable.
- Captured browser startup output is bounded and used in launch failure diagnostics; saved snippets come from a configurable snippets directory.
- The source supports browser automation and custom snippets, but I found no source-grounded attack behavior.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/dockerChromeForTesting-BMmEQq88.mjsView on unpkg · L1A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/dockerChromeForTesting-BMmEQq88.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @agimon-ai/po-browse-tool@0.30.14-alpha.2.
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.30.14-alpha.2 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.