Commands

Choose a command by task, or find it alphabetically in the sidebar. Each command has a dedicated page. Run flog help <command> for the complete help supported by your installed version.

flog check and flog format are experimental. Their subcommands and options may change before stabilization; the canonical machine-readable command list is experimental-commands.json at the repository root. Experimental status does not relax safety or refusal guarantees.

Resolve and install dependencies#

Command	Purpose
`flog init`	Initialize a project, lock, and install
`flog install`	Install the exact locked graph
`flog lock`	Deliberately resolve dependencies
`flog add`	Add dependencies
`flog remove`	Remove dependencies
`flog upgrade`	Plan and confirm dependency upgrades
`flog audit`	Audit exact locked versions for vulnerabilities

Run workspace work#

Command	Purpose
`flog build`	Build source workspaces in dependency order
`flog run`	Run package scripts
`flog x`	Execute an installed local binary
`flog check`	Run read-only project checks (experimental)
`flog format`	Format supported source files (experimental)

Inspect and authenticate#

Command	Purpose
`flog view`	Read a field from published package metadata
`flog deprecate`	Set or clear one version's deprecation message
`flog login`	Authenticate with a registry
`flog whoami`	Verify registry credentials
`flog logout`	Remove a registry credential

Pack and publish#

Command	Purpose
`flog bump`	Plan coherent workspace release versions
`flog pack`	Create npm-compatible archives
`flog publish`	Preflight and publish packages

Maintain Flog#

Command	Purpose
`flog update`	Update the Flog executable

Help and version#

Command	Purpose
`flog help`	Show top-level or command help
`flog version`	Print the installed version

Common selection and output flags#

Flags are command-specific; check command help before combining them. Workspace-aware commands generally use --workspace <selector> for a package name, path, owned file, or glob, while --cwd <directory> changes discovery or the default package context. Commands that support --json document their confirmation and failure behaviour in the detailed guides.