@agimon-ai/po-browse-tool@0.30.14-alpha.4
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 manifest has no install hook, and the inspected command, dynamic import, and network request have package-related functions. The scanner hints do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines no install lifecycle hooks; its scripts are development and build commands.
- The CommonJS and ESM entrypoints dispatch browser operations through the package’s browser tool handler.
- Chrome for Testing metadata is fetched from the Google Chrome Labs endpoint for the browser installer.
- The package loads TypeScript snippets from a configured snippets directory; this is user-configured runtime code execution.
- The flagged child process runs Git in a supplied working directory to resolve local repository metadata.
- The flagged command output is used to resolve a local Git directory; the inspected code does not send it over the network.
- The dynamic import loads configured local snippets, and the inspected network request serves Chrome for Testing setup.
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.4.
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.4 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.