@agimon-ai/po-browse-tool@0.0.0-alpha.52
MCP server for browser automation using Playwright with profile management, page registry, and multi-browser support
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe static signals reflect browser automation and process-management behavior, with output surfaced as launch-failure diagnostics. The package and inspected dependencies declare no install lifecycle hooks, and inspection did not establish credential theft or an unrelated command-output transfer.
Decision evidence
public snapshot- The manifest points consumers to the inspected runtime entrypoints and declares no install lifecycle hook.
- The runtime entrypoints load browser automation and process-management dependencies.
- The runtime handles an explicit browser launch operation and checks its profile and browser type.
- Browser process output is buffered for launch-failure diagnostics; the failure details are surfaced as an error to the caller.
- The inspected dependency manifests have no install lifecycle hooks, and their entrypoints expose port-registry, process-registry, and validation utilities.
- The process and network capabilities identified by static signals fit browser management and support functions; inspection did not establish an unrelated command-output recipient or install-time attack.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @agimon-ai/po-browse-tool@0.0.0-alpha.52.
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.52 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.