@agimon-ai/po-browse-tool@0.0.0-alpha.63
MCP server for browser automation using Playwright with profile management, page registry, and multi-browser support
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe scanner’s process and network signals correspond to browser lifecycle and configurable telemetry code in the inspected entrypoints. The manifest has no install lifecycle hook, and the prepared local dependency sources inspected are ordinary registry and validation helpers.
Decision evidence
public snapshot- The package entrypoints expose the CommonJS and ES module builds; its scripts are for building, development, testing, type checking, and linting.
- The flagged runtime operation validates the requested profile and browser type before launching the bound browser.
- Process execution is used to inspect process relationships and start Chrome with browser arguments; no shell command or unrelated output transfer was identified in those paths.
- The inspected prepared dependencies provide port registry, process registry, and schema validation exports; their manifests show development scripts rather than install hooks.
- Telemetry endpoints are selected from OpenTelemetry environment settings or package-specific endpoint settings; no fixed unrelated collector was identified.
- The Playwright test stub statically re-exports test bindings, and the extension entry begins with browser link and telemetry code.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @agimon-ai/po-browse-tool@0.0.0-alpha.63.
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.63 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.