Glossary
The words the modernization report and the dashboard use, in the order a run meets them.
The repository and the branch
Original commit. The commit your repository was at when the run started. Every comparison in the report is against it.
Apply branch. The branch Azilos creates for its changes. It carries the version edits, the regenerated lockfile and any approved fix. Azilos never commits to your default branch.
Lockfile. The file that records the exact version of every installed package:
package-lock.json for npm, pnpm-lock.yaml for pnpm, yarn.lock for Yarn. After Azilos edits
versions it regenerates the lockfile on the branch, so the branch installs exactly what it declares.
Upgrade policy. A project's standing choice of what a plan may contain: patch and minor versions only, or major versions too, and whether the Node.js runtime is upgraded.
Excluded upgrade. An upgrade someone on your team removed from the plan. It does not appear on the branch, and the report names who excluded it.
Validation
Apply validation. The check of the branch against the original commit. Azilos runs install, then build and test, on both, each in its own container. Build and test run only if the repository defines the script.
Step. One command of a validation: install, build or test. Each step ends as one of:
| Status | Meaning |
|---|---|
| passed | The command exited with success. |
| failed | The command exited with an error. |
| timed out | The command did not finish in the time allowed. |
| not run | An earlier step did not pass, so this one never started. |
| not defined | The repository has no such script, so there was nothing to run. |
Baseline. The steps that passed on the original commit. They are what the branch is measured against.
Verdict. What the comparison says about one step:
| Verdict | Meaning |
|---|---|
| regression | Passed on the original commit and fails on the branch. |
| fixed | Did not pass on the original commit, passes on the branch. |
| passed on both | Passed on the original commit and on the branch. |
| failed on both | Failed on both, so the upgrade did not cause it. |
| not compared | A side did not run this step, or neither defines it. |
Regression. A step that passed on the original commit and fails on the branch. It is the only result that asks for a fix.
Inconclusive. No step passed on the original commit, so there is no baseline and the branch could not be checked for regressions. An inconclusive validation is never reported as clean, and Azilos does not deploy or open a pull request for it.
Fixes
AI fix proposal. The code change an AI model proposes for a regression: the files it would edit and why each edit fixes the failure. A proposal changes nothing until someone approves it.
Approval. A person on your team accepting a proposal. The edits are committed to the Apply branch and the validation runs again. A rejected proposal commits nothing.
Consent. Your team's decision, taken by an admin, that a capability may send data outside your install. Without it the capability is skipped.
Paying for AI
Credits. The prepaid balance on Azilos Cloud that AI requests are charged against. One credit pack is bought first, and each request is charged at the token counts the AI vendor reports.
Azilos API key. The key your install uses to spend your credits. It is shown once, when you create it on your account page, and can be revoked there.