Integrations
LPM.dev Registry works with CI jobs, deployment platforms, and webhook endpoints. Each integration uses its own credential.
| Need | Integration | Start here |
|---|---|---|
| Install private, Pool, or Marketplace packages in CI | A read token in LPM_TOKEN for LPM CLI or an npm-compatible client | CI/CD |
| Publish from GitHub Actions or GitLab CI | A Trusted Publisher that gives the job a 15-minute publish token for one package | Trusted Publishers |
| Pull an encrypted environment in CI | An env OIDC policy and a project key that LPM.dev Registry stores encrypted | OIDC for CI |
| Synchronize application environments | LPM CLI connections to Vercel, Coolify, Fly.io, Railway, or GitHub Actions | Platform integrations |
| Install private, Pool, or Marketplace packages during a deployment build | A read token in a build variable or a Docker BuildKit secret | Deployment platforms |
| Receive organization or personal events | An HTTPS endpoint that verifies the version 2 HMAC signature | Outbound webhooks |
Package access in CI
LPM CLI reads the token from LPM_TOKEN:
npm install -g @lpm-registry/cli
lpm ci
If the project installs with npm, pnpm, or Yarn 1, run lpm setup ci npmrc before the install. The command writes the token into the .npmrc file of the job:
lpm setup ci npmrc
npm ci
You can also commit a .npmrc that reads the token from LPM_TOKEN. CI/CD shows both options.
Create a read token in the personal or organization token settings. Store it in the encrypted secret store of the CI provider.
Give the token only to the steps that need LPM.dev Registry access.
Trusted publishing
A Trusted Publisher lets a GitHub Actions or GitLab CI job publish one package without a long-lived publish token.
Set these values on the "Trusted publishers" page of the package:
- The repository owner and name.
- The workflow file.
- One exact branch or tag ref, or one tag pattern such as
refs/tags/v*. - An environment, if the job uses one.
When you save, LPM.dev Registry looks up the immutable numeric repository ID or GitLab project ID and stores it. You can also enter the ID yourself.
In the job, run:
lpm publish -y
LPM CLI exchanges the job's OIDC token for a 15-minute publish token for that package.
Trusted Publishers are separate from install tokens, env OIDC policies, and Sigstore provenance.
A configuration without the numeric ID and the allowed ref cannot publish. Select "Replace" on each such configuration and enter both values.
Encrypted environments
An env OIDC policy lets a CI job pull an environment of a personal Pro project or an organization project:
lpm env oidc allow --allow-server-decryption --provider=github --repo=owner/repository \
--workflow=.github/workflows/deploy.yml --branch=main --env=production
lpm env pull --oidc --env=production --output=.env
Run the first command on a development machine. It prints a policy ID. Run the second command in the CI job, with the policy ID in LPM_OIDC_POLICY_ID.
The policy gives no access to publish packages. OIDC for CI explains the policy, the key escrow, and the provider requirements.
Platform environment sync
LPM CLI can synchronize selected environment values directly with these platforms:
- Vercel
- Coolify
- Fly.io
- Railway
- GitHub Actions
Platform credentials and connection settings are separate from LPM.dev Registry package tokens. Platform integrations explains the supported operations and the security boundaries.
See also
- CI/CD explains package installs and Trusted Publisher workflows.
- Deployment platforms explains Vercel, Netlify, and Docker builds.
- Outbound webhooks explains signature verification, replay limits, and idempotency.
- Local secrets explains how to manage project environment values with LPM CLI.
- The LPM CLI CI/CD guide explains installation, caching, and quality-gate behavior.