@debugg-ai/debugg-ai-mcp
Zero-Config, Fully AI-Managed End-to-End Testing for all code gen platforms.
This report shows the evidence for @debugg-ai/debugg-ai-mcp@6.1.1. 0 of 12 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3h ago · by lpm-firewall-aiThe package enables runtime telemetry by default and sends a Git-derived repository name to PostHog, a detail not disclosed in its telemetry event description. The hashed telemetry ID and opt-out reduce exposure, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The runtime config embeds a PostHog project key so telemetry is sent by default.
- Project lookup telemetry includes `repoName` in its event properties.
- The package derives `repoName` from the Git origin remote as an `owner/repo` value.
- The README discloses project lookup telemetry and an opt-out, but does not list `repoName` among the captured event fields.
- The README says the API key is hashed for the telemetry distinct ID and provides a way to disable telemetry.
- The package’s stated purpose includes sending user-requested test workflow data to DebuggAI’s API.
Source & flagged code
5 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/handlers/testPageChangesHandler.jsView on unpkgPackage contains a possible secret pattern.
dist/handlers/testPageChangesHandler.jsView on unpkg · L67Hardcoded password in dist/handlers/testPageChangesHandler.js
dist/handlers/testPageChangesHandler.jsFindings
Affected versions and remediation
This report applies to @debugg-ai/debugg-ai-mcp@6.1.1.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @debugg-ai/debugg-ai-mcp@6.1.1 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.