lean-package-research

Evaluating a Lean 4 package for adoption requires running structured discovery and health checks on the repository and Lake dependencies. This produces an evidence-based recommendation detailing whether to add, update, fork, pin, vendor, or reject the package.

A Lean package adoption decision framework assesses candidate packages and toolchain health to output a compact package card. This card summarizes validation steps, sequencing plans, and evidence for integrating new repositories.

Adjusting Lake package pins involves assessing toolchain health and dependency compatibility. A structured evaluation provides a sequencing plan with validation requirements to safely execute pin adjustments or vendor packages.

Yes, Lean package evaluation is applicable to both Reservoir and GitHub Lean repositories. It performs health checks and dependency classification to generate integration recommendations for either source.

Forking or vendoring a Lean package is recommended when health checks reveal toolchain incompatibilities or insufficient maintenance. The evaluation output classifies the package and sequences the fork or vendor action with required validation steps.