pm-user-repository

The pm user repository is a community registry of package definitions for pm. Its ur module lets pm install packages from Lua definitions hosted in the repository: you write a short config, ur downloads and runs the definition, and pm uses the returned table to fetch, build and install the binary.

1. You download ur.lua into your pm config directory.
2. Your init.lua requires it and calls ur.Fetch { ... } for each package.
3. ur.Fetch downloads the Lua file from the repository over HTTPS, loads it in text-only mode (which blocks bytecode injection) and pcalls it to get the table.
4. pm consumes the table to handle download, build and install.

The ur.Github helper covers the common case: fetch a tarball from a GitHub repository, extract it, run make (or a custom build command) and return the artifact path. It can use gh auth token for authenticated API requests (5000 requests per hour instead of 60).

Download the module:

$ mkdir -p ~/.config/pm && curl -o ~/.config/pm/ur.lua https://raw.githubusercontent.com/hugoocoto/pm-user-repository/refs/heads/main/ur.lua

Then use it from init.lua:

local ur = require("ur")

Packages = {
    ur.Fetch { user = "hugoocoto", file = "nvim-nightly/nvim.lua" },
    ur.Fetch { user = "hugoocoto", file = "helium/helium.lua" },
}

All of them are under the hugoocoto user directory.

Each .lua file returns a table:

return {
    url = "https://github.com/neovim/neovim/releases/download/nightly/nvim-linux-x86_64.appimage",
    name = "nvim",
    build = "chmod +x nvim",
}

1. Fork the repository.
2. Create a directory named after your GitHub username.
3. Add your .lua files inside it (subdirectories are fine, like username/tool/tool.lua). A README.md next to it renders on the docs page.
4. Open a pull request. CI validates the Lua syntax and the root structure.

• Source code (MIT)
• Package documentation