proxify
v0.0.16 open-sourceThe section your link pointed to isn't on proxify's page any more, so we've brought you to the top.
Proxify is a proxy tool that intercepts, dumps, filters, and manipulates HTTP/HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. and non-HTTP traffic, with upstream HTTP/SOCKS5SOCKS5A proxy protocol that relays TCP and UDP traffic through an intermediary server without inspecting it, letting cyber tools tunnel connections through firewalls or pivot hosts with minimal overhead. proxy support.
proxify -of yaml -o output.yaml proxify -config-directory /path/to/custom/config proxify -jsonl proxify -update proxify -vv
Summary
Proxify is an open-source MIT-licensed HTTP/HTTPS proxy that intercepts, filters, and manipulates traffic, including non-HTTP protocols via plugins for things like XMPP, SMTPSMTPThe application-layer protocol used to send email between servers and from clients to servers; cyber tools use it to relay alerts, phishing simulations, or exfiltrated data over standard mail infrastructure., FTP, and SSH. It runs as a command-line tool, deployed standalone or pointed at from another proxy, with a DSL for matching and rewriting requests in flight, TLS MITM with client/server certificates, full traffic dumps to jsonl or yaml, and a native embedded DNS server. It suits penetration testers and application security engineers who need a scriptable interception layer rather than a full manual testing client; its own README describes replaying captured traffic into Burp Suite by setting proxify as the upstream proxy, so it complements rather than replaces that workflow. First committed in 2020, it has drawn 30 contributors and 28 commits over the past year, though its last release was 357 days ago.
Proxify is a proxy tool that intercepts, dumps, filters, and manipulates HTTP/HTTPS and non-HTTP traffic, with upstream HTTP/SOCKS5 proxy support.
How proxify helps
Which requests and responses actually crossed the wire during this test run?
dumps full traffic to jsonl or yaml, including request bodies alongside headers, so a POST or PUT payload can be checked after the fact rather than reconstructed from memory
Which requests match a pattern I care about, and can I change them before they go out?
evaluates each request/response against a DSL expression and rewrites matching traffic in flight, so filtering and manipulation happen without a manual replay step
Can I point my thick client or CLI tool at this and still see its traffic?
runs as a standalone MITM proxy with client/server TLS certificates and an embedded DNS server, so invisible clients that don't support manual proxy configuration still get intercepted
How do I get this captured traffic into Burp for manual follow-up?
sets itself as the upstream proxy for a replay pass, resending dumped requests with their original domain names so Burp receives them as if seen live
What non-HTTP protocols can I still inspect without writing a parser?
ships plugins that decode specific protocols such as XMPP, SMTP, FTP, and SSH, exposing them in the same traffic dump rather than raw bytes
Can I chain this in front of another proxy I'm already using?
accepts an upstream HTTP or SOCKS5 proxy, so traffic can be forwarded onward after filtering instead of terminating there
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for proxify, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail proxify puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Commercials
pricing & packaging history · ProjectDiscovery vendor page23 readings of ProjectDiscovery's pricing page since Feb 2024, with 7 relaunches of its plan lineup and 4 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
projectdiscovery.io, every changeProjectDiscovery's home page and 3 more pages as they looked each month from August 2021 to October 2026: 18 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
10 entries
No entries match these filters.
- August 20251
- March 20241
- February 20241
- August 20231
- July 20231
- March 20231
- October 20221
- June 20221
- November 20211
- May 20211
Project health
Issue, contributor and maintainer activity in projectdiscovery/proxify, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 −5 vs prior 12 months
- Maintainers 0 +0 joined · −1 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed 14% of issues opened, last 12 months
- Median time to close 1.1 days first maintainer reply 27 hours
- Open backlog 1 of 114 issues ever filed
- Issues opened / month 0 · 5 communitymaintainers
- Open backlog 1
- Contributors / month 0
- Commits / month 0
- Stars 3,073
- bugs 43%
- features 14%
- other 43%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.