feat(package-vulnerability-scanner): show the specific reason a scan or read failed - #460
Draft
amylin1249 wants to merge 4 commits into
Draft
feat(package-vulnerability-scanner): show the specific reason a scan or read failed#460amylin1249 wants to merge 4 commits into
amylin1249 wants to merge 4 commits into
Conversation
This was referenced Jul 29, 2026
amylin1249
force-pushed
the
pvs-08-error-surfacing-ui
branch
from
July 29, 2026 17:50
ff1e136 to
4137c0b
Compare
Contributor
Extension release summary😴 Changed but won't releaseThe following extensions have code changes but the manifest version hasn't been incremented:
If you intended to release these changes, update the See the contributing guide for details. |
amylin1249
marked this pull request as draft
July 31, 2026 15:43
amylin1249
force-pushed
the
pvs-08-error-surfacing-ui
branch
from
August 1, 2026 01:32
4137c0b to
54f799a
Compare
amylin1249
force-pushed
the
pvs-08-error-surfacing-ui
branch
from
August 1, 2026 01:50
54f799a to
eb71c43
Compare
amylin1249
force-pushed
the
pvs-08-error-surfacing-ui
branch
4 times, most recently
from
August 1, 2026 05:46
4dea165 to
ddfe2a6
Compare
amylin1249
force-pushed
the
pvs-08-error-surfacing-ui
branch
2 times, most recently
from
August 1, 2026 16:02
5ac1c01 to
0db3728
Compare
…or read failed VulnerabilityChecker.vue and ContentCard.vue now show the actual detail (content.packageFetchError.message, scannerStore.scanError) instead of a one-size-fits-all message, and a "Not scanned" badge distinguishes a failed scan from "no vulnerabilities found". Adds a loading state for the vulnerability lookup itself, so a card with loaded packages doesn't briefly report "no vulnerabilities" before the scan actually finishes.
…l links, dropped unintentionally
… inside its own v-else-if Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
amylin1249
force-pushed
the
pvs-08-error-surfacing-ui
branch
from
August 1, 2026 16:38
0db3728 to
78e2dcb
Compare
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
1 participant
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.
Split out of #428 into small, reviewable PRs (tracking issue #415). Stacked 8/10 — stacked on #459, merge bottom-up.
VulnerabilityChecker.vueandContentCard.vuenow show the actual failure detail instead of a one-size-fits-all message, with a "Not scanned" badge distinguishing a failed scan from "no vulnerabilities found", plus a loading state for the vulnerability lookup itself so a card doesn't briefly report a false zero.This is where @karawoo's review comment on #428 lands: the per-item reason from Connect (
e.error_message, not the full JSON dump) now reaches the user instead of being swallowed behind fixed text.