NodeSecure / NodeSecure/report

Ideas to improve UI (HTML & PDF)

Open
#258 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
JavaScript
Stars
15
Forks
16
Avg merge
2m
Merged PRs (30d)
5

Description

Hello 👋

There is a lot of room to improve that project, however it kinda hard to make definitive issues about things to improve (since it highly depend on UI ideas ..).

Here some of my ideas:

Improving Authors & Maintainers section

Current section doesn't bring much values (has we only see some avatars in the PDF). I think a list would be better here (with maybe a podium with the top 3 maintainers?).

image

Having list of impacted files and packages for others graphics

Most graphics allow to get a global overview of the situation. However it could be cool to allow the user to configure in RC if he want to be alerted of few things, for example:

  • Please show me the list of files (and packages) with extension .exe
  • Please show me the packages with warnings obfuscated-code or shady-link

Add missing metrics from Scanner payload

  • Number of minified files (overall / by packages)
  • Missing dependencies
  • Vulnerabilities

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 reviewing the existing HTML and PDF report UI and how Scanner payload metrics are represented. The issue lists several possible improvements, so first narrow it to one concrete change and identify the relevant report entry points. Done should mean an agreed UI or metric enhancement is implemented and verified in both requested output formats where applicable.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.