Explanation¶
These pages explain why OSS IQ reports what it reports. Read them before you trust a
recommendation in CI or hand it to a coding agent. They follow the order of a run: what status
measures, how plan picks an update, and what apply writes.
Start with The update pyramid, which shows the five update strategy tiers in one diagram. For flags and fields, see the reference. For tasks, see the how-to guides.
What OSS IQ measures¶
A scan gathers the evidence that status reports and that every recommendation rests on.
Page |
What it answers |
|---|---|
How OSS IQ judges whether a package is still maintained and whether a CVE is being exploited, and how the two meet in one triage verdict |
|
Why OSS IQ reports where each version constraint comes from, and who can change the version it holds |
|
What each external source feeds, what breaks when it degrades, and where that shows |
How OSS IQ picks an update¶
OSS IQ picks at most one target version for each direct dependency, and plan lists the result.
Page |
What it answers |
|---|---|
How far up the version ladder a package may go, tier by tier, and what choosing a tier risks |
|
Which three questions OSS IQ answers before it recommends a version, and how to read the result |
|
Why a package is allowed to move at all, and what a missing source does to that |
|
When each tier withholds a package, bumps it in range, widens the range or crosses a major, as a table and a flowchart per tier |
|
Why a release must age before OSS IQ recommends it, and what skips the wait |
|
Which runtime a release is checked against, and where that check fails open |
|
The target version, |
What OSS IQ writes¶
apply is the only command that changes your manifest and lockfile.
Page |
What it answers |
|---|---|
What each command reads and writes, how |