@agimon-ai/po-browse-tool@0.0.0-alpha.16
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 inspected runtime behavior supports bound browser automation and snippet execution. The scanner’s command, network, and dynamic import flags do not establish an attack in the inspected source.
Decision evidence
public snapshot- package.json lists development and build scripts, with no install lifecycle hook.
- The CommonJS entrypoint exposes browser operations through a bound runtime and restricts browser launches to the configured profile.
- The ESM entrypoint has the same bound browser launch behavior.
- The Chrome helper fetches version information as part of its Chrome for Testing support.
- The container bundle dynamically imports scripts compiled from TypeScript for its snippet functionality.
- The container bundle’s `fetch` call is a health check, not evidence of command-output exfiltration.
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.16.
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.16 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.