You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 578b63e
Browse filesBrowse the repository at this point in the historyBrowse files
Classify purls through Ecosystem::from_purl in free files (#747) (#1126)
* Start refactor for #747
Assisted-by: Claude Code:claude-opus-5-5
* Classify purls through Ecosystem::from_purl
Seven production checks spelled a purl type prefix inline
(`starts_with("pkg:npm/")` and friends) in the Bun and vlt vendor
preflights, the PyPI fuzzy matcher, the Coursier sidecar retry and VEX
verification. They now ask `Ecosystem::from_purl`, the one map from purl
type to ecosystem, so a change to the type vocabulary has one place to
land.
No behavior change: a table test shows `from_purl(p) == Some(eco)`
holds exactly when `p` starts with that ecosystem's prefix, near misses
included. A one-sided source-scan guard fails on any new file that
spells a prefix inline; the 16 files open PRs change are listed as
pending for the next slice of #747.
Assisted-by: Claude Code:claude-opus-5-5
* List main's new inline purl checks as pending
main gained inline purl-type prefix checks in six production files
after this branch was cut. The one-sided guard would have failed on
them once merged. List them as pending for #747's next slices so the
guard passes on main as it stands; migrating them stays out of this
slice.
Assisted-by: Claude Code:claude-opus-5-5
* Classify NuGet stale-install purls via from_purl
main added an inline pkg:nuget/ prefix check in the hosted NuGet
stale-install remedy after this branch last merged main, which the
guard rejects. Route it through Ecosystem::from_purl like the other
migrated checks; the answer is unchanged (see the table test).
Assisted-by: Claude Code:claude-opus-5-5
---------
Co-authored-by: Claude <noreply@anthropic.com>
0 commit comments