diff --git a/index.html b/index.html
index abe073f..49f0f1e 100644
--- a/index.html
+++ b/index.html
@@ -85,6 +85,7 @@
"Network kill switch via pf anchor — block the inspected app's outbound traffic",
"VM mode — analyse risky apps inside a macOS VM via guest agent",
"Reports export as JSON, HTML, or PDF",
+ "privacycommand command-line tool for scripting, CI, previewing Homebrew cask updates and risk-gated upgrades, with zsh, bash and fish tab completion",
"Local-first — analysis stays on your machine, no telemetry"
]
}
@@ -152,6 +153,14 @@
"text": "The same things you could find with codesign, otool, plutil, fs_usage, sfltool, and a stack of grep, except cross-referenced and explained. The difference is consistency: privacycommand runs every detector against every drop, in the same shape, and explains every finding in plain English so the report is shareable with someone who isn't a binary-analysis nerd."
}
},
+ {
+ "@type": "Question",
+ "name": "Can I use it from Terminal or in CI?",
+ "acceptedAnswer": {
+ "@type": "Answer",
+ "text": "Yes. The app comes with a privacycommand command-line tool that runs the same analyzer. Homebrew installs put it on your PATH; with the disk image, use Install Command Line Tool… in the privacycommand menu. Use --json for machine-readable output and --warn-exit to fail a CI job on findings. Tab completion is available for zsh, bash and fish."
+ }
+ },
{
"@type": "Question",
"name": "Can I export reports for a ticket or a vendor review?",
@@ -522,7 +531,7 @@
.brand-lockup .mark img { width: 100%; height: 100%; }
.brand-lockup .name { font-weight: 700; font-size: 1.05rem; letter-spacing: -0.01em; }
nav.topnav ul.links { display: flex; gap: 22px; list-style: none; margin: 0; padding: 0; }
- nav.topnav ul.links a { color: var(--slate); font-size: 0.95rem; font-weight: 500; }
+ nav.topnav ul.links a { color: var(--slate); font-size: 0.95rem; font-weight: 500; white-space: nowrap; }
nav.topnav ul.links a:hover { color: var(--ink); }
.theme-toggle {
width: 40px; height: 40px; border-radius: 999px;
@@ -535,7 +544,9 @@
.theme-dark .theme-toggle .icon-moon { display: none; }
.theme-dark .theme-toggle .icon-sun { display: block; }
- @media (max-width: 760px) {
+ /* 840px, not 760px: with the Command line link the nav needs that much
+ room before the links collapse, or the page scrolls sideways. */
+ @media (max-width: 840px) {
nav.topnav ul.links { display: none; }
/* The row's own padding wipes out the container gutter, which left the
brand and Download button flush against the screen edges. */
@@ -994,6 +1005,7 @@
- Features
+ - Command line
- FAQ
- About
- Install
@@ -1407,6 +1419,39 @@ Claims vs. binary
+
+
+
+
+
+
Command line
+
The same analyzer, from Terminal.
+
The app comes with a command-line tool of the same name. Audit an app by name or path, get JSON for a CI job, or run privacycommand preview to check your outdated Homebrew casks before brew upgrade replaces them. privacycommand upgrade --max-risk medium goes a step further: it upgrades the casks that stay within that risk limit and holds the riskier ones for you to review.
+
A Homebrew install puts privacycommand on your PATH, with tab completion for zsh, bash and fish. With the disk image, use Install Command Line Tool… in the privacycommand menu. The tool lives inside the app, so it updates with it. It ships in the app from the release after 0.1.5.
+
Command-line setup
+
+
+
+
+
+ Terminal — zsh
+
+
+
+
% privacycommand Calculator --short
+
✓ Calculator (com.apple.calculator) — Nothing noteworthy — low risk (0/100).
+
% privacycommand preview --min-tier ⇥
+
critical high low medium
+
# ~/.zshrc, if you didn't install with Homebrew
+
eval "$(privacycommand completion zsh)"
+
+
+
+
+
+
+
+
@@ -1456,6 +1501,12 @@
The questions that come up first
The same things you could find with codesign, otool, plutil, fs_usage, sfltool, and a stack of grep, except cross-referenced and explained. The difference is consistency: privacycommand runs every detector against every drop, in the same shape, and explains every finding in plain English so the report is shareable with someone who isn't a binary-analysis nerd.
+
+ Can I use it from Terminal or in CI?
+
+
Yes. The app comes with a privacycommand command-line tool that runs the same analyzer. Homebrew installs put it on your PATH; with the disk image, use Install Command Line Tool… in the privacycommand menu. Use --json for machine-readable output and --warn-exit to fail a CI job on findings. Tab completion is available for zsh, bash and fish.
+
+
Can I export reports for a ticket or a vendor review?
@@ -1531,6 +1582,7 @@ Build from source
Product