@agimon-ai/po-browse-tool@0.0.0-alpha.17
MCP server for browser automation using Playwright with profile management, page registry, and multi-browser support
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected runtime behavior matches browser automation and Chrome setup. Scanner signals for process execution, dynamic imports, and networking do not establish malicious behavior in the inspected source.
Decision evidence
public snapshot- package.json lists the package entrypoints and contains no install lifecycle script.
- Both runtime entrypoints check the requested browser launch against the bound profile and browser type.
- The runtime supports loading TypeScript snippets from its configured snippets directory as part of browser automation.
- The Chrome helper retrieves version metadata from the Chrome for Testing feed.
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.0.0-alpha.17.
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.17 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.