privacy-filter

LLM privacy gateway in Go, millisecond-latency PII and secret redaction. Used in production by PackyCode.

Runssource: GitHubhomepageGoMITcommit 64b8de3c2060

Go, MIT licensed. The project labels itself: ai gateway, data redaction, gitleaks, golang, grpc, http server, llm security and middleware.

privacy-filter runs. An Argusic agent installed it in 4.7 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Both binaries build, all 3153+28 tests pass, HTTP server serves /health /redact /redact/batch correctly with 221 gitleaks rules loaded, gRPC server starts on :8089, and benchmarks show sub-ms latency on 2KB text.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
341
forks
42
open issues
3
watchers
0
size
0 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
5 minutes
Cold machine to finish
3 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
go test ./... passed (3153/3153 bulk + 28 unit tests); HTTP GET /health returned 200 with status ok; POST /redact correctly redacted PII and secrets; POST /redact/batch worked; gRPC server started and listened; benchmarks completed
Model tokens used
97,127
Exact commit tested
64b8de3c2060
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**Tests**: `go test ./filter/...` — 3153/3153 bulk scenarios passed, all 28 unit tests passed, benc…
**HTTP service**: `GET /health` returned `{"gitleaks_rules":221,"skipped_rules":0,"status":"ok"}`. …
**gRPC service**: Started and listened on `:8089`.
**No errors encountered** — everything worked out of the box after Go was made available.
tokens used
97,127
All systems operational. Here's the summary:
**Install**: `go build` succeeded for both `server-http` and `server-grpc` using Go 1.25.0 toolchai…
**Tests**: `go test ./filter/...` — 3153/3153 bulk scenarios passed, all 28 unit tests passed, benc…
**HTTP service**: `GET /health` returned `{"gitleaks_rules":221,"skipped_rules":0,"status":"ok"}`. …
**gRPC service**: Started and listened on `:8089`.
**No errors encountered** — everything worked out of the box after Go was made available.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 4.7 minutes, faster than the median of the 23 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 24 ai-gateway projects Argusic has installed and timed, privacy-filter was the 10th fastest to reach a running state, and 18 of 24 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 4.7 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

ai-gatewaydata-redactiongitleaksgolanggrpchttp-serverllm-securitymiddlewarepii-detectionprivacyredactsecrets-detection

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/privacy-filter.svg)](https://argusic.com/subject/privacy-filter)

Questions

Does privacy-filter run?
Yes. privacy-filter runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test privacy-filter?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 64b8de3c2060. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test privacy-filter?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does privacy-filter take to install?
4.7 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does privacy-filter need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing privacy-filter?
Nothing did, in the recorded run: zero errors between clone and running.
How does privacy-filter compare with the alternatives?
Of the 24 ai-gateway projects Argusic has installed and timed, privacy-filter was the 10th fastest to reach a running state, and 18 of 24 reached one at all.
Where is the evidence for privacy-filter?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion