Repository navigation
Releases
v0.2.3
ceynox-watch 0.2.3
Nothing new to type. This one is about how far you have to take our word for things, which is now slightly less far.
-
Provenance you can hold. The release carries its signed build provenance as a file,
ceynox-watch-0.2.3.intoto.jsonl, beside the archives. It ties each archive to the workflow run that built it:gh attestation verify ceynox-watch-0.2.3-linux-x86_64.tar.gz --repo CeyNova-Labs/ceynox-watch
-
Fuzzed parsers. The three parsers that read input nobody here controls (DNS replies, the packet capture on macOS, kernel type information) now have fuzz targets, run on every change. Tens of millions of runs in, they have found nothing, which is the boring outcome we were hoping for.
-
A pinned build image. The toolchain container is named by digest, so it cannot change underneath a build.
-
A security address. Reports can go to security@ceynovahq.com as well as through GitHub's private form.
SECURITY.mdsays what happens next. -
Two badges. The project now has an OpenSSF Scorecard and an OpenSSF Best Practices badge. The Scorecard is not a perfect ten, and the link says exactly why: the repository is young and has one maintainer. We would rather show the number than wait for it to flatter us.
The program itself is the same as 0.2.2. If you are on 0.2.2, upgrading changes nothing you will notice.
brew upgrade ceynox-watchv0.2.2
ceynox-watch 0.2.2
0.1.0 told you what a command did. This one helps with the three questions that came next: what would it do if I ran it, is that different from last week, and can a machine check that for me.
Inspect a package before it is on your laptop
ceynox-watch --inspect npm:some-package@1.2.3
ceynox-watch --inspect pypi:some-package -- python -c 'import some_package'The install runs in a throwaway container, as an unprivileged user with an empty home directory, and you get the usual record. It works from macOS too, with full Linux detail. "Just try it and see" is now a thing you can do without also donating your SSH keys to the experiment.
docs/gallery has the records of five well-known packages, so you know what boring looks like. (One of them downloads 332 MB from a second host during install. It is a browser. It is fine. It is still nice to be told.)
Compare with last time
ceynox-watch --write-baseline install.json -- npm ci # once
ceynox-watch --baseline install.json --fail-on new -- npm ciA baseline is a small JSON file: programs run, hosts contacted, catalog locations touched, areas written to. Later runs say what they did that the baseline did not, and --fail-on new turns that into exit status 3. The package you have trusted for five years gets one free pass, and then it has to behave the same way twice.
A GitHub Action
- uses: CeyNova-Labs/ceynox-watch@v0.2.2
with:
run: npm ci
baseline: .github/ceynox-watch.json
fail-on: newThe report goes in the job summary. A dependency bump that changes what the install does becomes a failed check on the pull request that caused it, which is a better place to find out than the incident review.
Also
- How much was sent. On Linux every TCP connection reports the bytes that went each way, and anything over 100 kB out gets a line of its own.
- Drop-off hosts. Connections to paste sites, file drops, chat webhooks, request catchers, tunnels and dynamic DNS hosts are flagged by name.
- Reports.
--report run.htmlwrites one self-contained page;--report run.mdwrites Markdown for an issue or a pull request. - AI agent configuration. Writes to the settings, instructions and MCP server lists of Claude Code, Codex, Gemini CLI, Cursor, Windsurf, Claude Desktop and VS Code are flagged. An install script has no business editing what your agent is told.
npx,uvxand friends. Processes of a package fetched and run in one go are labelled with it, which is how most MCP servers get started.
Worth knowing
--inspectneeds Docker. The container starts empty and nothing is planted in it, so a package that only misbehaves when it finds credentials will look better there than it is. A container is also not a virtual machine.- Transfer sizes are TCP only, and Linux only.
- The macOS archive is larger: it now carries the Linux builds that
--inspectruns inside the container.
Install or upgrade
brew install ceynova-labs/tap/ceynox-watch # or: brew upgrade ceynox-watchArchives and SHA256SUMS are below.
(0.2.2 is 0.2.1 with a shorter description for the Action, so that the GitHub Marketplace will have it. There is no 0.2.0: its release build tripped over a check of our own, which is what checks are for.)
v0.2.1
ceynox-watch 0.2.1
0.1.0 told you what a command did. This one helps with the three questions that came next: what would it do if I ran it, is that different from last week, and can a machine check that for me.
Inspect a package before it is on your laptop
ceynox-watch --inspect npm:some-package@1.2.3
ceynox-watch --inspect pypi:some-package -- python -c 'import some_package'The install runs in a throwaway container, as an unprivileged user with an empty home directory, and you get the usual record. It works from macOS too, with full Linux detail. "Just try it and see" is now a thing you can do without also donating your SSH keys to the experiment.
docs/gallery has the records of five well-known packages, so you know what boring looks like. (One of them downloads 332 MB from a second host during install. It is a browser. It is fine. It is still nice to be told.)
Compare with last time
ceynox-watch --write-baseline install.json -- npm ci # once
ceynox-watch --baseline install.json --fail-on new -- npm ciA baseline is a small JSON file: programs run, hosts contacted, catalog locations touched, areas written to. Later runs say what they did that the baseline did not, and --fail-on new turns that into exit status 3. The package you have trusted for five years gets one free pass, and then it has to behave the same way twice.
A GitHub Action
- uses: CeyNova-Labs/ceynox-watch@v0.2.1
with:
run: npm ci
baseline: .github/ceynox-watch.json
fail-on: newThe report goes in the job summary. A dependency bump that changes what the install does becomes a failed check on the pull request that caused it, which is a better place to find out than the incident review.
Also
- How much was sent. On Linux every TCP connection reports the bytes that went each way, and anything over 100 kB out gets a line of its own.
- Drop-off hosts. Connections to paste sites, file drops, chat webhooks, request catchers, tunnels and dynamic DNS hosts are flagged by name.
- Reports.
--report run.htmlwrites one self-contained page;--report run.mdwrites Markdown for an issue or a pull request. - AI agent configuration. Writes to the settings, instructions and MCP server lists of Claude Code, Codex, Gemini CLI, Cursor, Windsurf, Claude Desktop and VS Code are flagged. An install script has no business editing what your agent is told.
npx,uvxand friends. Processes of a package fetched and run in one go are labelled with it, which is how most MCP servers get started.
Worth knowing
--inspectneeds Docker. The container starts empty and nothing is planted in it, so a package that only misbehaves when it finds credentials will look better there than it is. A container is also not a virtual machine.- Transfer sizes are TCP only, and Linux only.
- The macOS archive is larger: it now carries the Linux builds that
--inspectruns inside the container.
Install or upgrade
brew install ceynova-labs/tap/ceynox-watch # or: brew upgrade ceynox-watchArchives and SHA256SUMS are below.
(There is no 0.2.0. Its release build tripped over a check of our own, which is what checks are for.)
ceynox-watch 0.1.0
The first release. It answers a question you were probably happier not asking: what did that command actually do?
pip install says "Successfully installed". npm install says "added 2 packages". Your AI coding agent says "Done!". All three statements are true, and none of them mention the part where something read your SSH key. ceynox-watch is for the part they leave out.
ceynox-watch -- pip install some-packageWhat it shows
- Every program started, as a tree, so you can see that the "install" was really a shell running a script running another script.
- Every network destination, by name.
pypi.orgis expected. Anything after that is a conversation starter. - Every file written, and every read of a place secrets live: SSH keys, cloud credentials, registry tokens, browser profiles, shell history,
.envfiles. - Which package did it. Install scripts are attributed to the npm or PyPI package they belong to, so the blame lands somewhere specific.
- Folder listings of
~/.ssh,~/.awsand friends, because looking around tends to come right before taking.
It flags; it does not judge. npm reading ~/.npmrc is npm doing its job, and it's listed anyway. You're the one who knows whether a "date formatting library" has business with your AWS credentials.
Platforms
| Linux | macOS | |
|---|---|---|
| How | eBPF, hooked at the kernel's security layer | the system's built-in sandbox, in report-only mode |
| Needs | root, via sudo, for the part that needs it |
nothing: no root, nothing installed |
| Watch a command | yes | yes |
| Attach to a running process, or the whole machine | yes | no |
| Network detail | host name and address | port only; --hosts adds names and addresses (uses sudo) |
Things we'd rather tell you now than have you find out
- It's a record, not a sandbox. By the time you read that a key was opened, it was opened. This is the smoke detector, not the sprinkler system.
- macOS sees less than Linux. No attaching to running processes, and programs that sandbox themselves won't run under it. Apple does not allow a sandbox inside a sandbox, and we asked nicely.
- The macOS binary isn't signed with an Apple certificate. Homebrew installs work; a browser download needs one
xattrcommand, which the README gives you. Yes, a security tool asking you to bypass a security warning. The irony is noted. The checksums and the build are public so you don't have to take it on faith. - Recent npm blocks install scripts by default, which is the correct decision and slightly ruins our best demo. pip still runs whatever
setup.pysays, so the demo uses that. - A process running as root can hide from this, as it can from any tracing tool.
The README lists the rest.
The tool's own manners
Written in Rust, with no unsafe in the user-space program. On Linux the privileged part gives up root as soon as the kernel programs are loaded; on macOS it never has root at all. It has no telemetry, no update check and no network access, which is less a feature than the bare minimum for a tool whose pitch is "see what software does behind your back".
Install
brew install ceynova-labs/tap/ceynox-watchOr download the archive for your system below and check it against SHA256SUMS. Linux binaries are static; the macOS binary runs on Apple silicon and Intel.
Showing is half of it
ceynox-watch tells you what happened, after it happened, on the one machine where you remembered to run it. CeyNox Security is what we build for the other half: watching every device all the time, reviewing every package installed, and stopping the bad ones in milliseconds. It's in closed beta, and the waitlist is open.