# ChYing is a Burp-style proxy and scanner written in Go with a Vue front end

> ChYing is an open source interactive penetration testing tool that combines a proxy with repeater, intruder and decoder in a Wails desktop application, and it also embeds the author's separate automated scanner so both styles of testing sit in one place.

**yhy0/ChYing** — 承影，愿你在光影之间，找到属于自己的锋芒。开源的类 BurpSuite 应用 ChYing — may you find your own edge between light and shadow. An open-source, BurpSuite-like application.

- Repository: https://github.com/yhy0/ChYing
- Stars: 782 · Forks: 72
- Language: Go
- License: not declared
- Published: 2026-10-20 · Updated: 2026-10-20 · Language: en
- Canonical page: https://hysenlabs.com/projects/yhy0-chying

## The split between interactive and automated testing is the product idea

The author's account of why the project exists is that they wanted to build a security product as widely used as Xray or Burp Suite, and that their earlier project Jie was a comprehensive web security assessment tool supporting active and passive scanning, vulnerability detection and information gathering, which collected 600 plus stars. The problem with Jie, as the readme puts it, is that it leaned towards automated scanning, the kind of tool you run and forget. What was missing was an interactive penetration testing platform that can capture traffic, modify it, replay it and brute force it, like Burp Suite, but lighter, more modern and more personal. So ChYing was built, and Jie's scanning capability was integrated into it, with the two described as complementary, one interactive and one automated. That framing explains the feature set better than a list of tools would.

## The four Burp-style tools it actually implements

The core features are organised as four familiar tools. The HTTP proxy captures HTTP and HTTPS traffic in real time and offers smart filtering by method, host, status code and path, with a right-click menu to send a request to the repeater, the intruder or the scanner. The repeater lets you modify a request manually and test it repeatedly, with multiple tabs so that you can compare tests side by side. The intruder performs automated attack testing with support for several payload types and shows results in real time. The decoder converts between URL, Base64, Hex and Unicode, computes MD5 and SHA hashes, and supports chained decoding. The readme also lists a plugin module covering JWT parsing and key brute forcing, Swagger API testing for unauthorized access and injection detection, 403 bypass, and Shiro decryption, which is the kind of feature set that only makes sense for someone with an authorisation to test the target.

## The stack is Go, Vue 3 and Wails, with SQLite for storage

The technology stack section is specific. The backend is Go, chosen for performance and cross platform support, and the front end is Vue 3 with TypeScript. The framework is Wails v3, described as the combination of Go and the web. Storage is SQLite for lightweight local persistence, and the scanning engine is Jie. The dependency list in go.mod backs the picture up in detail, with a mitmproxy.go file and a mitmproxy/ directory at the repository root indicating the interception layer, and dependencies for HTTP and proxy work from projectdiscovery including proxify, rawhttp and martian, plus retryabledns and interactsh for out of band interaction testing. There is also an nmap binding, a JWT library, a browser automation library in both chromedp and go-rod, and mark3labs/mcp-go, which suggests the application exposes tool functionality over the Model Context Protocol. The repository also carries extension.go, so the tool surface is designed to be extendable.

## A Go desktop app with a task runner, a Docker CLI and an agent harness

The repository layout tells you more about how the project is built than the readme does. Alongside main.go and app.go there is a family of app_ prefixed files, app_config.go, app_database.go, app_initialization.go, app_oast.go, app_proxy.go, app_scan.go and app_utils.go, which is the pattern of a Wails application where each subsystem is a separate file bound to the front end. There is a build/ directory, a Taskfile.yml for task automation, a Dockerfile.cli and a docker-compose.cli.yml, which points to a headless command line mode alongside the desktop application. The api/ directory, the cmd/ directory, the pkg/ directory, the lib/ directory and the frontend/ directory separate the Go surfaces from the web assets. Then there are skills/, a skills directory, plus AGENTS.md, CLAUDE.md and a project_runtime.go with a project_runtime_test.go, and given the mcp-go dependency the tool is being prepared to be driven by an agent rather than only by a person. The go.mod targets go 1.26, which puts the floor high.

## Two years in a private repository, then opened in 2026

The history section is unusual and worth reading because it sets expectations about the codebase. The first version was built in April 2023 with Wails and Vue, providing a basic proxy, directory scanning and JWT parsing, with a rough interface that worked, and it collected 400 plus stars after being open sourced. Then came a dormant period in 2023 and 2024 when the author's work was busy and the project stopped updating, followed by a refactoring phase in 2024 and 2025 conducted in a private repository with 137 commits. The readme gives a candid account of why the interface improved: the author's own front end skills were limited, and tools like Cursor changed that, because they no longer had to work out how an animation effect was implemented or whether a layout should use flex or grid. The readme is also direct about the reason for open sourcing now, that the project sat in a private repository for nearly two years because it never felt good enough, and that perfection is the enemy of open source.

## What the project is honest about

The readme says plainly that the tool is not meant to replace Burp Suite, which remains the most professional and comprehensive penetration testing tool, and then lists who might still want this one: people who want a lighter tool that starts faster, a more modern interface, an open source scheme they can modify, or simply an example of how one security engineer built their own tooling. The licence position is the notable gap. The project metadata records the licence as unknown, and there is no licence file among the top level repository entries, which for a codebase someone explicitly says you can modify is the first thing to sort out before building on it. The scope of the scanning side is also narrower than the feature list suggests. Passive traffic scanning and active vulnerability detection for XSS, SQL injection, SSRF and command execution are listed, with Nuclei POC support, but the readme is a product announcement rather than a reference, and it does not describe which detection rules exist, how false positives are handled, or what the update cadence for the rule set is.

## Conclusion

ChYing suits a security engineer who wants a Burp-style interactive testing environment that starts quickly, runs on a desktop rather than in a browser, and can be modified, since the whole thing is a Go and Vue codebase with an MIT style open source release. It is the wrong tool for a large commercial assessment where a licensed product with a support contract and a mature extension ecosystem is required, and it is the wrong tool if you want the automated scanning side only, since the project is explicit that the interactive half is the point and the scanner is integrated as a complement. Before evaluating it, note that the licence field is empty and there is no licence file among the repository entries, and that the interface is documented in Chinese with an English readme alongside it, so the depth of the English documentation is limited. The last push was on 2026-09-01 and the current release is v2.2.0 from the same day.

## FAQ

### What is ChYing?

ChYing is an open source, BurpSuite-like application for interactive penetration testing, written in Go with a Vue 3 and TypeScript front end on Wails v3, using SQLite for local storage. It offers an HTTP proxy, a repeater, an intruder, a decoder and plugin modules.

### How does ChYing relate to the Jie project?

Jie is the author's earlier comprehensive web security assessment tool, supporting active and passive scanning, vulnerability detection and information gathering. The readme describes Jie as leaning towards automated scanning, the kind of tool you run and forget, so ChYing was built to fill the interactive gap, and Jie's scanning capability was integrated into it as the automated complement.

### What tech stack does the ChYing desktop application use?

A Go backend, a Vue 3 and TypeScript front end, the Wails v3 framework, SQLite for local storage and the Jie scanning engine. The repository also contains a Dockerfile.cli and a docker-compose.cli.yml for a command line mode, and a skills/ directory alongside AGENTS.md and CLAUDE.md files.

## Sources

- [Issues](https://github.com/yhy0/ChYing/issues)
- [README](https://github.com/yhy0/ChYing/blob/main/README.md)
- [Releases](https://github.com/yhy0/ChYing/releases)
- [yhy0/ChYing on GitHub](https://github.com/yhy0/ChYing)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/yhy0-chying