Engines Pinned
nodejs.engines-pinned
Ensures the engines.node field is set in package.json. Pinning the Node.js engine version prevents compatibility issues across environments.
Compatible Integrations
This guardrail works with the following integrations. Click to see how to use Engines Pinned with each collector.
Enable This Guardrail
Add the parent policy to your lunar-config.yml to enable this guardrail.
policies:
- uses: github://earthly/lunar-lib/policies/nodejs@v1.0.0
include: [engines-pinned]
# with: ...How This Guardrail Works
This guardrail is part of the Node.js Project Guardrails policy. It evaluates data collected by integrations and produces a pass/fail check with actionable feedback.
When enabled, this check runs automatically on every PR and in AI coding workflows, providing real-time enforcement of your engineering standards.
Learn How Lunar Works →Configuration Options
These inputs can be configured in your lunar-config.yml to customize
how the parent policy (and this guardrail) behaves.
| Input | Required | Default | Description |
|---|---|---|---|
min_node_version
|
Optional |
18
|
Minimum required Node.js major version (e.g., "18", "20") |
min_node_version_cicd
|
Optional |
18
|
Minimum required Node.js major version for CI/CD commands (e.g., "18", "20") |
Node.js Project Guardrails
This guardrail is part of the Node.js Project Guardrails policy, which includes 5 guardrails for devex build and ci.
Ready to Automate Your Standards?
See how Lunar can turn your engineering wiki, compliance docs, or postmortem action items into automated guardrails with our 100+ built-in guardrails.
Infrastructure conventions
Post-mortem action items
Security & compliance policies
Testing & quality requirements