aws-runtime-bridge@1.9.168
⚠ Under reviewAgentsWorkStudio runtime bridge service for machine-level agent runtime integration
AI Security Review
scanned 11d ago · by lpm-firewall-aiInspected source supports ordinary browser setup and authenticated, caller-directed agent configuration; it did not establish malicious behavior. The required clean citations cover 17 distinct paths while the schema permits 16, so this is manual review due to citation coverage, not an identified attack.
Decision evidence
public snapshot- The install hooks call local setup scripts; the inspected browser setup selects a user-provided or recognized mirror host and installs Playwright Chromium.
- The indicated config code resolves a Claude settings path, but that location alone does not establish an unconsented configuration change.
- The AI-source route applies caller-supplied configuration behind runtime-token authentication, and the application code skips tools that are not installed.
- The inspected authentication middleware validates runtime tokens or panel sessions for protected operations.
Source & flagged code
28 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to aws-runtime-bridge@1.9.168.
See all versions of aws-runtime-bridge for other recorded verdicts.
- Review the evidence and your use of aws-runtime-bridge@1.9.168 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.