feat(inspector): track trusted publisher and staged publish as supply chain signals - #208
Merged
Merged
Conversation
… chain signals `NpmMeta.provenance` used to be a `'trustedPublisher' | boolean` union. Split it into three independent booleans (`provenance`, `trustedPublisher`, `staged`) and surface them everywhere as one "supply chain score" — how many of the three a package carries. - badge: 3 signals is a green seal, 2 teal, 1 blue, 0 an amber warning; the tooltip spells out which ones are present - grid: the Provenance tab becomes Supply Chain, grouped by score (All 3 Signals / 2 of 3 / 1 of 3 / No Signals) - dependency composition bar: SIGNED/UNSIGNED becomes the same four buckets - `showProvenanceBadge` setting is renamed to `showSupplyChainBadge`; a stored value for the old key is ignored and falls back to the default
sxzz
force-pushed
the
feat/supply-chain-signals
branch
from
September 16, 2026 06:31
4c34b28 to
1754700
Compare
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NpmMeta.provenancewas a'trustedPublisher' | booleanunion, which could only ever express one signal at a time. npm now exposes three independent ones, so this splits them apart and surfaces them together as a supply chain score — how many ofprovenance/trustedPublisher/stageda package carries.Changes
provenance?: boolean+ newtrustedPublisher?: booleanandstaged?: boolean, populated fromfast-npm-meta.ProvenanceBadge.vue→SupplyChainBadge.vue): colored by score — 3 a green seal, 2 teal, 1 blue, 0 an amber warning. The tooltip spells out which signals are present, e.g.This package is signed with provenance by a trusted publisher (staged publish). The show/hide setting now keys off the score, so the "Absent" mode no longer shows a green check on a package that has a signal but no provenance.Provenancetab becomesSupply Chain(/grid/supply-chain), grouped by score —All 3 Signals/2 of 3 Signals/1 of 3 Signals/No Signals, each with a tooltip naming the three signals. Old/grid/provenancelinks fall back to the Depth grouping.PercentageProvenance.vue→PercentageSupplyChain.vue):SIGNED/UNSIGNEDbecomes the same four buckets (3/3…0/3).app/utils/supply-chain.ts, shared by all three.:provenanceattribute onDisplayPackageName, which has no such prop.Note
The
showProvenanceBadgesetting is renamed toshowSupplyChainBadge. A value stored under the old key is ignored and the setting falls back to its default (present); no migration is included.Verification
pnpm test(134 passed),pnpm lintandpnpm typecheckclean.