l3montree-dev / l3montree-dev/devguard

Dependency Risks: Export Table

Open
#2,914 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request
Dominant language
Go
Stars
161
Forks
43
Avg merge
1d 8h
Merged PRs (30d)
37

Description

Is your feature request related to a problem? Please describe.
I would like to export the Dependency Risk table as a simple PDF containing CVEs + LIb + Score to make it possible to share this information with a supplier for a given software artefact - instead of a full fledged PDF export with 30 pages of "information that are publicly available".

Describe the solution you'd like

A PDF export with a single table, with e.g. CVE + Lib + Score and optionally "Manufacturer rating" as an empty column.

Additional context
Table in question:

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Dependency Risk table and the existing full PDF export path, then inspect how the table's CVE, library, and score data is assembled. Done means a PDF export for one software artefact containing the requested single table, with the optional manufacturer-rating column considered.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.