Limier exposes four top-level commands:
limier runlimier inspectlimier renderlimier version
Use this to compare one dependency upgrade in an isolated fixture.
limier run \
--ecosystem npm \
--package left-pad \
--current 1.0.0 \
--candidate 1.1.0 \
--fixture fixtures/npm-app \
--scenario scenarios/npm.yml \
--rules rules/default.yml \
--report out/limier/report.json \
--summary out/limier/summary.md \
--evidence out/limier/evidenceFlags:
--ecosystem: ecosystem adapter to use--package: dependency name to compare--current: baseline version--candidate: candidate version--fixture: path to the sample application directory--scenario: path to the scenario manifest--rules: path to the rules file--report: path for the JSON report, defaultreport.json--summary: path for the Markdown summary, defaultsummary.md--evidence: directory for evidence files, defaultevidence
Supported ecosystems today:
cargonpmpip
Use this when you already have a report.json file and want a concise explanation without rerunning the fixture.
limier inspect --input out/limier/report.jsonFlags:
--input: existingreport.json--output: optional output file for the inspection text
Use this to turn an existing report into a downstream surface such as a CI summary or PR comment.
limier render --format build-summary --input out/limier/report.jsonFlags:
--format: one ofgithub-comment,gitlab-note, orbuild-summary--input: existingreport.json--output: optional output file
Print the current Limier version:
limier versionLimier also supports simple logging controls through environment variables:
LIMIER_LOG_LEVEL:debug,info,warn, orerrorLIMIER_LOG_FORMAT: set tojsonfor structured output; any other value, or leaving it unset, uses the default text format
Example:
LIMIER_LOG_LEVEL=debug LIMIER_LOG_FORMAT=json limier run ...