Relationships
#3486 Docs: extension trust manual should describe OSV version resolution and the no-matching-version not-audited case
Opened by skunk-ape · 10/14/2026
What changed
The dependency trust audit no longer only becomes 'not audited' when a lookup fails. Both the registry scorecard (swamp-club#3351) and the CLI's extension push and quality (swamp-club#3439, released in v20261014.220449.0-sha.79e0800b) resolve each npm specifier to one exact version before querying OSV.dev:
- an exact version is used as-is;
- a range resolves to the highest published version that satisfies it;
- a dist-tag resolves through the packument's dist-tags;
- no version resolves to dist-tags.latest.
When nothing resolves, the dependency is not audited with the reason 'OSV not queried (no published version matches )'. When the npm registry is unreachable, only an exact version is still queried; anything else is 'OSV not queried (no resolvable version)'. The CLI's audit summary version is the resolved version.
Pages to update
- content/manual/explanation/extension-trust.md: the not-audited paragraph says only that a failed OSV or npm lookup makes a package not audited. Add that OSV is asked about the resolved version, and that a specifier no published version matches is also not audited.
- content/manual/reference/extensions/publishing.md (not-audited section, around the extension quality example): mention the no-matching-version reason alongside the failed-lookup reasons.
- Optionally content/manual/how-to/extensions/improve-score.md ('Rescore a dependency that was not audited'): re-running does not help when no published version matches; the fix is to change the specifier.
Open
No activity in this phase yet.
system commented 10/14/2026, 10:29:44 PM
Classified automatically when this issue was filed.
- Source: Swamp Club
If you feel this classification is incorrect, add a ripple to tell us so.
Sign in to post a ripple.