Alternatives
Products that do what Graveyard does
One dead-code scanner for mixed-language repos
- 1AD
2021 · tech.nextroll.com
- 2CA
Hey! We are presenting CodeTracer - a user-friendly time-traveling debugger designed to support a wide range of programming languages: https://github.com/metacraft-labs/codetracer?tab=readme-ov-f... CodeTracer records the execution of a program into a sharable self-contained trace file. You can load the produced trace files in a GUI environment that allows you to move forward and backward through the execution and to examine the history of all memory locations. They say a picture is worth a thousand words — well, a video is even better! Watch the demo below to see…
2025 · github.com
- 3SC
2020 · grep.app
- 4
- 5GA
What works now: user signups, org creations, private/public repos, and importing GitHub repositories (both as read-only mirrors and full migrations). So basically, you can create, push and pull to a repo, but we don't have many features quite yet (issues, PRs, CI). What is a bit unique is: 1) we built it in Rust and 2) the website is a little odd. Its design is inspired by CLIs (e.g., fzf, broot, vim) instead of web apps, and as such, lacks some affordances that you might typically expect in favor of keyboard-driven instant navigations (we have the very ambitious goal of an FCP of…
Jun 2026 · gitdot.io
- 6DR
I'd like to invite everyone to try out DontBeEvil.rip, an experimental search engine for developers. tl;dr $ alias rip="curl -G -H 'Accept: text/plain' --url https://dontbeevil.rip/search --data-urlencode " $ rip 'q=Heartbleed bug' DontBeEvil.rip is a year long experiment to see if a small team can build a developer-focused search engine that is self-sustaining on $10 monthly subscriptions. It works by only indexing high-quality resources that are relevant to developers. You won't get useless listicles because we'll never crawl them. Relevant urls are harvested from HN,…
2022
- 7
- 8DM
I wrote this Go project to implement a dead man’s switch that didn’t rely on cron jobs, timers, databases, etc on the infra it runs on. Deadcheck integrates to PagerDuty and keeps a long running incident snoozed until expected check-in times where it’ll alert unless a check-in occurs.
2024 · github.com
- 9
- 10FC
Debugging a crash can sometimes feel like a noir detective story: following faint clues, chasing red herrings, and eventually hitting the moment where the whole case finally makes sense. I leaned into that idea and built Fatal Core Dump, a small game where the investigation is real crash debugging. The game gives you a Linux binary, its core dump, a source file, and some logs. You solve the mystery by debugging it. The premise: an engineer dies when an airlock on an asteroid mining station opens unexpectedly. Your job is to determine whether it was a simple software bug or something more…
Mar 2026 · robopenguins.com
- 11DA
I've done this same println debugging thing so many times, along with some sed/awk stuff to figure out which call was causing the issue. Now it's a small Go package. With some `runtime.Callers` I can usually find the spot by just swapping the existing Mutex or RWMutex for this one. Sometimes I switch the mu.Lock() defer mu.Unlock() with the LockFunc/RLockFunc to get more detail defer mu.LockFunc()() I almost always initialize it with `deadlog.New(deadlog.WithTrace(1))` and that's plenty. Not the most polished library, but it's not supposed to land in any commit, just a temporary…
Feb 2026 · github.com
- 12
- 13
You write a standard solution, just like on LeetCode, and run it through the CLI. It identifies the problem by ID or title, executes your code against local test cases, and shows the result. It currently supports around 1.4k problems and multiple languages, including Python, C++, Rust, Java, Go, TypeScript, Swift, and others. The project is still an MVP. System design, SQL, and concurrency problems are not supported yet, but support for more problem types is planned. Made in Haskell!
19d ago · github.com
- 14
- 15IB
2024 · securelog.com
- 16RA
Hi HN — I’m learning Rust and decided to build a universal CLI for running code in many languages. The tool, Run, aims to be a single, minimal dependency utility for: running one-off snippets (from CLI flags), running files, reading and executing piped stdin, and providing language-specific REPLs that you can switch between interactively. I designed it to support both interpreted languages (Python, JS, Ruby, etc.) and compiled languages (Rust, Go, C/C++). It detects languages from flags or file extensions, can compile temporary files for compiled languages, and exposes a unified REPL…
Oct 2025 · github.com
- 17GA
2022 · github.com
- 18CA
2023 · github.com
- 19AI
I built this software to help users who need to do static code analysis for C/C++ codebase. This can help you to explore the ASTs interactively. It can replace the Clang ast dump completely and also you can search the code/ASTs in a structual way. For example you can search a function which matches specific name or number of paremeters.
May 2026 · uvic-aurora.github.io
- 20
Find deprecated npm packages before they haunt your prod app
May 2026 · stackgraveyard.dev
- 21AS
2024 · github.com
- 22DD
Hello friends, Today I'm sharing a little tool to help you explore GitHub repositories: • https://diggit.dev This project was admittedly a big dumb excuse to play with Elm and Claude Code. I published my design notes and all the chat transcripts here: • https://taylor.town/diggit-000 Please add bug reports and feature requests to the repo: • https://github.com/surprisetalk/diggit Enjoy!
2025 · diggit.dev
- 23BG
We originally set out to solve complex debugging headaches and useless alerts caused by traditional security scanners in our own projects. Static Analysis (SAST) flagged too much noise because it couldn't verify runtime context, while Dynamic Analysis (DAST) missed internal logic bugs because it treated the app like a black box. We built a CLI tool to bridge this gap using grey box testing from a red team approach. We use internal knowledge of the codebase to guide parallel execution, allowing us to find complex or hidden logic errors and attack paths standard linters/scanners miss. The…
Dec 2025 · bloodhoundsecurity.ca
- 24TB
2018 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →