synapse-hub@2.6.0
Phien ban cu da duoc thu hoi. Vui long nang cap len synapse-hub@3.0.1 de su dung day du 51 skills va cac ban va bao mat moi nhat.
Enterprise AI Agent Intelligence Hub & Autonomous Skill Network
AI Security Review
scanned 21h ago · by lpm-firewall-aiThe launcher does not run its CLI at import time, and the inspected scanner credential reference is a pattern for detecting AWS credential paths rather than code that reads or sends credentials. The reported helper behavior aligns with the package's CLI and Playwright testing purpose.
Decision evidence
public snapshot- The package exposes bin/agent-qa.js as its CLI and main entry point.
- The launcher runs its CLI only when executed directly; importing it only exports resolvePython.
- The AWS credential path flagged by the scanner appears in a static detection pattern, not a credential-reading flow.
- The Playwright example starts a target project's local development server with shell=False and tears it down.
- The launcher can spawn a Python process when a CLI command is explicitly run, which is expected for this package's tool-dispatch purpose.
- The Playwright example uses subprocess and a local network connection, but only as part of an explicitly run browser-testing example.
Source & flagged code
6 flaggedSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
bin/agent-qa.jsView on unpkg · L3This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/agent-qa.jsView on unpkgFindings
Affected versions and remediation
This report applies to synapse-hub@2.6.0.
See all versions of synapse-hub for other recorded verdicts.
- Review the evidence and your use of synapse-hub@2.6.0 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.