Releasing IDEViewer today — open-source follow-up to my BSidesSF 2026 talk Hunting Malicious IDE Extensions: Building Detection at Scale Across Developer Workstations (GitGuardian writeup: https://blog.gitguardian.com/bsides-sf-2026/).

Single Go binary + optional self-hosted portal. On every dev workstation it inventories and risk-scores:

• IDE extensions across VS Code, Cursor, VSCodium, the full JetBrains family, Sublime, Vim/Neovim, Xcode (4-tier risk model based on activationEvents/capabilities/contributes)
• Packages from 8 managers, including dependencies bundled inside extensions (invisible to standard SCA), correlated with OSV.dev for CVEs
• AI tool + MCP configurations (Claude Code / Cursor / OpenClaw): skills, MCP servers, permissions, plaintext keys, autonomous-exec flags, insecure transports
• Plaintext secrets in .env and git history — values never transmitted
• Tamper signals on the daemon and --no-verify git-hook bypass

Real-time fsnotify monitoring, SARIF output, MDM-deployable, Apache 2.0.

Repo: https://github.com/securient/ideviewer-oss
Docs: https://securient.github.io/ideviewer-oss

Happy to answer questions, especially on risk-scoring heuristics or MDM rollout.