Neovim lazy-nvim

ID

lazy

Links

Documentation · Repository

Upstream stars

⭐ 21,610

Last commit

2025-12-17

Version requirement

>= 11

Platforms

🅱️ BSD · 🐧 Linux · 🍎 macOS · ⨂ Unix · 🪟 Windows

Operations

installed · upgrade_all

purl types

pkg:lazy/

CLI name

nvim

Every call

nvim --headless <command> -c cquit

Issues and PRs

📦 manager: neovim-based

Source

neovim.py

lazy.nvim is a modern plugin manager for Neovim.

lazy.nvim is a Lua plugin, not a standalone binary: each operation below is a Lua one-liner evaluated by a throw-away Neovim process. Plugins are Git clones under stdpath('data')/lazy, pinned by a lazy-lock.json lock file in stdpath('config') that records the exact commit of each one.

What mpm adds to lazy

mpm reaches across every manager at once, not lazy alone: mpm installed and mpm outdated cover lazy alongside every other manager you run in one table, mpm upgrade --all updates them together, and mpm sbom exports the whole machine as one bill of materials.

Every mpm command also gains --dry-run and --plan previews, cross-scheme version comparison and purl identifiers. See manager augmentations for how each one is built.

Operations

Operation

Supported

Notes

installed

✅

outdated

❌

The :Lazy check comparison reaches its result only through a private field no contract covers; upgrade --all still works.

orphans

search

install

❌

A plugin is installed only by declaring it in the user’s own Lua configuration, which mpm does not own.

upgrade

upgrade_all

✅

remove

❌

A plugin is removed only by dropping its spec from the user’s Lua configuration, which mpm does not own.

sync

cleanup

doctor

Configuration

  • Ignore lazy on the mpm CLI by passing the --no-lazy option.

  • Ignore it for every run in your configuration:

    [mpm]
    lazy = false
    
  • Raise the timeout of all lazy calls:

    [mpm.overrides.lazy]
    timeout = 900
    
  • Run mpm config-template lazy to print all overridable settings for your configuration file:

    [mpm.overrides.lazy]
    cli_names = [
        "nvim",
    ]
    cli_search_path = []
    dry_run = false
    ignore_auto_updates = true
    plan = false
    post_args = [
        "-c",
        "cquit",
    ]
    pre_args = [
        "--headless",
    ]
    pre_cmds = []
    requirement = ">=11.0.0"
    stop_on_error = false
    unmaintained = false
    version_cli_options = [
        "--clean",
        "--headless",
        "-c",
        "lua local p = vim.fn.stdpath(\"data\") .. \"/lazy/lazy.nvim\" if (vim.uv or vim.loop).fs_stat(p) then vim.opt.rtp:prepend(p) io.write(\"lazy.nvim \" .. require(\"lazy.core.config\").version) end os.exit(0)",
    ]
    version_regexes = [
        "lazy\\.nvim (?P<version>\\S+)",
    ]
    

The arguments and environment variables listed in the box atop this page are forced on every lazy call, so runs stay quiet, non-interactive and reproducible: the defaults you would set in CI anyway.

Recipes

A few jobs you would otherwise script around lazy, one mpm command each:

  • Snapshot and clone a machine: mpm --lazy dump lazy.toml, then mpm restore lazy.toml on the next one.

  • Export a compliance SBOM: mpm --lazy sbom (CycloneDX by default, --spdx for SPDX).

Privilege escalation

mpm runs this manager as the current user and never prepends sudo by default. Flip the policy for its privileged operations with --sudo or the per-manager sudo override.

None of its operations is privileged.

See privilege escalation for the full policy.

Cooldown

State of Neovim lazy-nvim’s release-age gating, from the cooldown support table:

Status: ❌ None

A cooldown only pays off where a compromised release can be withdrawn while the clock runs, and can only be emulated where the registry dates its releases. From the retraction table:

  • Registry: Upstream Git clones

  • Retraction: None: a plugin is cloned straight from its upstream repository, so withdrawing a bad revision is its author force-pushing, retagging or deleting it themselves. No index sits in between

  • Publish date: ❌ a commit or tag date is set by the author and freely rewritable

With --cooldown set, mpm skips this manager’s install and upgrade operations rather than run them unguarded (fail-closed); --cooldown best-effort opts back in.

Reference traces

A collection of raw native outputs captured from the manager’s own CLI and recorded in the manager source. If you know Neovim lazy-nvim well and a transcript below looks wrong, or a newer release changed its output format, report it.

$ nvim --headless --clean \
> -c 'lua local f = io.open(vim.fn.stdpath("config") .. "/lazy-lock.json") if f then io.write(f:read("a")) end os.exit(0)' \
> -c 'cquit'
{
  "lazy.nvim": { "branch": "main", "commit": "306a05526ada86a7b30af95c5cc81ffba93fef97" },
  "vim-sensible": { "branch": "master", "commit": "0ce2d843d6f588bb0c8c7eec6449171615dc56d9" },
  "z": { "branch": "master", "commit": "d37a763a6a30e1b32766fecc3b8ffd6127f8a0fd" }
}

Version check

The version is probed by running:

$ nvim --clean --headless -c lua local p = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if (vim.uv or vim.loop).fs_stat(p) then vim.opt.rtp:prepend(p) io.write("lazy.nvim " .. require("lazy.core.config").version) end os.exit(0)
lazy.nvim 11.17.5

and extracted with:

r"lazy\.nvim (?P<version>\S+)"

Upstream project

Metrics

folke/lazy.nvim

Activity

commit activity commits since open issues open pull requests

Popularity

forks watchers contributors

Metadata

latest release release date license main language

Changelog

  • 8.0.0 (2026-09-20)

    • Add the lazy.nvim Neovim plugin manager with installed and upgrade support. It declares no install or remove: lazy.nvim materializes only the plugin set the user’s own Lua configuration names.