Skip to content

fix(eol): expose dependency summary on scan components - #35

Merged
facundo-herodevs merged 1 commit into
mainfrom
fix/issue-429-dependency-summary
Sep 21, 2026
Merged

facundo-herodevs merged 1 commit into
mainfrom
fix/issue-429-dependency-summary

Conversation

@facundo-herodevs

@facundo-herodevs facundo-herodevs commented Sep 21, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Add the missing DependencySummary contract already returned by eol-api.
  • Require EolScanComponent.dependencySummary while allowing null when the SBOM dependency graph cannot be parsed.
  • Add compile-time contract coverage and document the exported type and null semantics.

Changes

File Change
src/types/eol-scan.ts Adds DependencySummary and declares EolScanComponent.dependencySummary as DependencySummary | null.
src/types/eol-scan.test.ts Verifies the API contract shape, nullability, and that the component field is required.
README.md Documents the new export and distinguishes unknown classifications from a null summary.

Review notes

This aligns the shared TypeScript contract with the existing report payload. It does not add or change runtime behavior.

Verification

  • npm run lint (Node 24)
  • npm run format:check (Node 24)
  • npm run type-check (Node 24)
  • npm run test (Node 22 and 24)
  • npm run build (Node 22 and 24)

Related to neverendingsupport/evergreen-ui#429

@facundo-herodevs
facundo-herodevs enabled auto-merge (squash) September 21, 2026 14:22
@facundo-herodevs
facundo-herodevs merged commit 7c7b32d into main Sep 21, 2026
7 checks passed
@facundo-herodevs
facundo-herodevs deleted the fix/issue-429-dependency-summary branch September 21, 2026 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants