Alternatives
Products that do what ExtGuard does
Audit the VS Code extensions already running on your machine
- 1
- 2
- 3
- 4
- 5
- 6
- 7AV
We made a VS Code extension [1] that lets you visualise logs and traces in the context of your code. It basically lets you recreate a debugger-like experience (with a call stack) from logs alone. This saves you from browsing logs and trying to make sense of them outside the context of your code base. We got this idea from endlessly browsing traces emitted by the tracing crate [3] in the Google Cloud Logging UI. We really wanted to see the logs in the context of the code that emitted them, rather than switching back-and-forth between logs and source code to make sense of what happened. It's a…
2025 · github.com
- 8IM
2024 · marketplace.visualstudio.com
- 9LC
Debugging is hard for LLMs, because they primarily depend on source code, and they don't have access to runtime state. I spent countless hours debugging code, and the only way I found LLMs useful for that, is to ask them to add log lines. That's annoying, because it pollutes my code and adds unnecessary diffs. So we made an MCP server that solve this problem. It gives MCP clients (like Claude Code) access to a NodeJS inspector, so they can: 1. set breakpoints 2. step in, step out, continue 3. fetch the current execution location 4. read console output 5. run JS using eval To try: 1. run a…
2025 · github.com
- 10GE
Hi! I've been frustrated with the secret sharing situation in serverside javascript land for a while; the common thing is to just toss .env files around on Slack to get someone's app working, or involves some kind of convoluted setup to get a blob from a storage and turn it into environment variables via commands I have to copy paste every time. But everyone uses secret storage providers, e.g. shared password vaults, cloud secrets, etc., so why not leverage those as URIs in a JSON file that can be checked in to source control? I want something simple that would just generate the darn .env…
2025 · github.com
- 11IB
2022 · npm.kasper.io
- 12
- 13AO
I’ve lost count of how many times a junior engineer accidentally pushed something into a dev branch that either contained secrets/credentials etc. or that leaked those into logs/std. out. Secure-log prevent logging for apps on production, scan for Secrets and remove them from logging. No more console.log().
2024 · github.com
- 14AV
I use print() a lot to debug small codebases. Log-booster VS Code extension allows you to insert/comment/uncomment/delete print statements within a Python file. If you happen to use it and like/dislike it, I would love to know. Inspiration: I discovered Turbo Console Log extension (https://github.com/Chakroun-Anas/turbo-console-log) and loved it. I noticed that it doesn't work for Python files. So I tried building one :)
2022 · github.com
- 15NJ
2015 · github.com
- 16TS
Hi HN, I’m Guillaume, the cofounder of Bearer, an Open Source SAST solution. After launching a few weeks ago here on Hacker News with support for Ruby and JavaScript stacks, I’m happy to report we’ve just released a new version (v1.2) with TypeScript support! In terms of code coverage, we use the same rules already implemented for vanilla JavaScript, but as usual, you can build your own. The rules list is here: https://docs.bearer.com/reference/rules/ It’s a first version for TS, but we believe that thanks to the pre-existing JavaScript support it should already…
2023
- 17SR
Hi Guys, I built SecretEnv to help solve one common thing that I have seen at every org, that I have worked at. We always had more than one password/credential manager. Service tokens maybe in Vault, AWS SSM etc and some team specific service account or temp account credentials being store in another password store such as 1Password or Keeper, there was never one single credential store. This is where SecretEnv comes in play, it runs any command with secrets injected as env vars, sourced from whatever combination of backend your team already uses. I am sure there are other tools as well…
May 2026 · github.com
- 18DI
I built an open-source malware detection daemon that monitors all running processes in real-time using ML + heuristics. No kernel modules or eBPF required. Key points: - Polls /proc for new processes (works on any Linux kernel 2.6+) - Random Forest model trained on EMBER 2018 dataset (2.3M samples) - Heuristic rules for crypto miners, ransomware, rootkits - ~20MB RAM, <1% CPU, sub-millisecond scan latency - Pure C, zero runtime dependencies - Model embedded directly in binary (50KB) Why I built this: Existing solutions either require modern kernels (eBPF) or are heavy/proprietary.…
Nov 2025 · github.com
- 19AN
Definition Stack is a new vscode extension I have just released. It is a reading tool for Javascript and Typescript. It is available in the extension marketplace. You just click in a function in any source code, execute a command, and a new tab opens next to the original. That tab has a "block" which contains a copy of the function you clicked in. In that code every word (symbol) that has a definition is highlighted. If you click on a higlighted word a new block opens above the original which contains the source code of the definition for that word. You can click in that block and repeat to…
2025 · github.com
- 20IJ
.env files have always felt archaic, insecure, clunky and honestly just not fun to work with. I see my friends (and myself) accidentally committing them all the time. Managing secrets across projects becomes a mess of copy-pasting keys into scattered env files with no real way to sync anything. So I built better-env: a secure, developer-friendly alternative to .env. Store your secrets once in a global encrypted store, and load them per-project at runtime. I’d love feedback on whether this feels useful beyond solo devs, and what you’d want for teams or CI setups. Fully open source:…
Nov 2025 · better-env.dev
- 21VV
Apr 2026 · vulnetix.com
- 22KC
Hi HN, I built KeyEnv because I was tired of the "can you Slack me the Stripe key?" workflow. The problem: My team's secrets lived in a mix of Slack DMs, shared Google Docs, and .env files that definitely weren't in .gitignore at some point. Enterprise tools like Vault required more DevOps time than we had. Doppler was close but felt heavier than we needed. What KeyEnv does: keyenv init # link project keyenv pull # sync secrets to local .env keyenv run -- npm start # inject secrets, run command That's basically it. Secrets are encrypted client-side (AES-256-GCM) before leaving your machine.…
Jan 2026 · keyenv.dev
- 23IB
Linux Foundation survey says 70-90% of modern software constitute OSS code. Yet we are stuck with tools that scan only for vulnerabilities in 3rd party libraries and that too with high degree of false positives. I built `vet` for policy and data driven analysis of 3rd party packages that goes beyond only vulnerability and allows codifying organisational policies related to OSS consumption. https://github.com/safedep/vet Looking forward to feedback and suggestions from HN :)
2023 · github.com
- 24EC
I participated in the Nvidia + Vercel 2 hour hackathon in SF tonight, and built something I've wanted, but hadn't tried building. I implemented an MCP Server and VS Code extension to allow Claude Desktop to place breakpoints, step through code, and execute expressions (assuming language support). So you can ask it a question that requires actually stepping through the code and now it can actually do that - check values for you, etc. It's _definitely_ not perfect. Have improvements? Please make a PR!
2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →