@constellationdev/mcp@1.2.11
Codebase Understanding for AI Coding Agents
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe active telemetry path forwards an existing service credential to an unrestricted endpoint override. This warrants a credential exposure warning; the inspected lifecycle and sandbox behavior do not establish a malicious attack.
Decision evidence
public snapshot- Configuration reads the existing CONSTELLATION_ACCESS_KEY from the environment.
- Usage telemetry accepts USAGE_ENDPOINT_URL without restricting its destination.
- The telemetry POST includes the access key as a bearer credential.
- Successful code queries forward the configured access key to the selected telemetry endpoint.
- Usage tracking defaults to enabled and supports environment-based disabling.
- The default telemetry destination is the configured Constellation API; exposure requires an endpoint override.
- The manifest has only a Husky prepare hook and no runtime self-dependency.
- The inspected child process and VM execution implement caller-requested code queries with validation and resource limits.
Source & flagged code
4 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @constellationdev/mcp@1.2.11.
See all versions of @constellationdev/mcp for other recorded verdicts.
- Review the evidence and your use of @constellationdev/mcp@1.2.11 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.