antiflock
Bootstrap and run AntiFl0ck — open-source
counter-surveillance for the networks you control — with one command. No manual
git clone, no hand-editing compose files.
Pre-alpha: this installs and runs the local, fully-simulated demo stack (Core, policy engine, signed audit log, Third-Eye dashboard). Host-level enforcement is still under active development — see the release status.
Requirements
- Docker
- git
- Node.js 20+ (the underlying stack's own build/dev tooling)
- Python 3.9+
Quick start
pipx install antiflock # or: pip install antiflock
antiflock init
antiflock dev
init clones the repo into ./antiflock (skipped if you're already inside a
checkout) and generates a private, locally-scoped config at
.antiflock/dev.env — operator/SDK/agent/dashboard tokens, never committed.
dev builds and starts the full stack. Once it's up, open
http://127.0.0.1:4173 — username operator, token from that config file.
Run the scripted coffee-shop simulation against a running stack:
antiflock lab
Stop everything:
antiflock down
Commands
| Command | Does |
|---|---|
antiflock init |
Clone (if needed) and generate local config |
antiflock dev |
Build and start the full local stack |
antiflock lab |
Run the one-shot coffee-shop simulation |
antiflock build |
Build images without starting them |
antiflock down |
Stop the local stack |
antiflock clean |
Stop and remove local stack volumes |
Flags: --dir <path> (checkout location, default ./antiflock), --ref <git-ref>
(branch or tag to clone, default main).
Feature configuration
.antiflock/dev.env— generated secrets and node/application identifiers (permissions locked down automatically; regenerate by deleting the file and re-runninginit).configs/demo.yamlanddocker-compose.ymlin the checkout — service ports, demo-mode flags, and thelabprofile.- Full walkthrough: docs/operator-runbook.md.
Already have a checkout?
Run any command from inside it and the CLI uses that directory directly instead
of cloning a new one — it's just a thin wrapper around
node scripts/compose.mjs.
Also on npm: npx antiflock (package) — same CLI, same commands.
License
Apache-2.0, see LICENSE. AntiFl0ck is an independent open-source project; see TRADEMARKS.md.
Metadata
Release files for antiflock 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| antiflock-0.1.1.tar.gz | 8.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| antiflock-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.4 kB
Release files / antiflock-0.1.1.tar.gz
| Download URL | antiflock-0.1.1.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e9bd4e7ac69fd400a3c8bee9f08acf7a12d0300fb780626228e14b55c760ec8
|
|
BLAKE2b-256 checksum How to use checksums |
74d879306a88bcfa64e325be6231710d166e56be6fbda3c18d040ffffca6d24b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logRelease files / antiflock-0.1.1-py3-none-any.whl
| Download URL | antiflock-0.1.1-py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a34208a30832335d28e1b13e07a487ee5b7b02647d9817e298c92c3f57640f73
|
|
BLAKE2b-256 checksum How to use checksums |
7b9cb7964fc14b80e87d1826d9c1d07cf2f1de3088aaea9c854b78ad8579254a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency log