Code analysis
static source read inferred
Static code-analysis findings — hidden prompt content in shipped skill files, committed secrets, dynamic-exec sinks, and suspicious call-home endpoints — across the analyzed catalogue. Heuristic, pure, no code executed; every row deep-links to its source. Click a kind to filter.
50020 analyzed
8131 re-analysis due
988 not analyzable
1 not yet analyzed
4803 source gone
not analyzable
789 too large 199 no source
Running analyzer v33. The scanner changelog explains what each version detects and when it changed.
- hidden prompt 338
- committed secret 6177
- dynamic exec 11826
- obfuscation 3575
- suspicious endpoint 12346
- credential in log 713
- over-broad oauth scope 2548
- suspicious skill script 185
- bundled IDE extension 49
- skill file 187620
- HIGH dynamic exec ruvector new Function()
new Function(stripped); - HIGH dynamic exec ruvector new Function()
const ret = new Function(getStringFromWasm0(arg0, arg1)); - MEDIUM suspicious endpoint @sentry/mcp-server sentry.io (telemetry)
"get_issue_tag_values(issueUrl='https://sentry.io/issues/PROJECT-123/', tagKey='browser')", - MEDIUM suspicious endpoint @sentry/mcp-server my-org.sentry.io (telemetry)
"get_issue_breadcrumbs(issueUrl='https://my-org.sentry.io/issues/PROJECT-123/')", - MEDIUM suspicious endpoint @sentry/mcp-server my-organization.sentry.io (telemetry)
"get_issue_activity(issueUrl='https://my-organization.sentry.io/issues/PROJECT-123/')", - MEDIUM suspicious endpoint @sentry/mcp-server sentry.sentry.io (telemetry)
"get_issue_details(issueUrl='https://sentry.sentry.io/issues/6916805731/?project=4509062593708032&query=is%3Aunresolved')", - MEDIUM suspicious endpoint @sentry/mcp-server us.sentry.io (telemetry)
typically the region-specific URL like 'https://us.sentry.io'. For self-hosted Sentry installations, this parameter is usually not needed and should be omitted. You can find the correct regionUrl from - MEDIUM suspicious endpoint @sentry/mcp-server sentry.io (telemetry)
"get_issue_tag_values(issueUrl='https://sentry.io/issues/PROJECT-123/', tagKey='browser')", - MEDIUM suspicious endpoint @sentry/mcp-server my-org.sentry.io (telemetry)
"get_issue_breadcrumbs(issueUrl='https://my-org.sentry.io/issues/PROJECT-123/')", - MEDIUM suspicious endpoint @sentry/mcp-server my-organization.sentry.io (telemetry)
"get_issue_activity(issueUrl='https://my-organization.sentry.io/issues/PROJECT-123/')", - MEDIUM suspicious endpoint @sentry/mcp-server sentry.sentry.io (telemetry)
"get_issue_details(issueUrl='https://sentry.sentry.io/issues/6916805731/?project=4509062593708032&query=is%3Aunresolved')", - MEDIUM suspicious endpoint @sentry/mcp-server us.sentry.io (telemetry)
typically the region-specific URL like 'https://us.sentry.io'. For self-hosted Sentry installations, this parameter is usually not needed and should be omitted. You can find the correct regionUrl from - HIGH credential in log agentdb credential in log
log.info(`Clients can connect using: agentdb sync connect <host> ${port} --auth-token ${authToken}`); - HIGH dynamic exec @payloadcms/plugin-mcp new Function()
return new Function('z', `return ${transpileResult.outputText}`)(z) - HIGH dynamic exec @payloadcms/plugin-mcp new Function()
return new Function('z', `return ${transpileResult.outputText}`)(z);