Link to CVE app does not preserve issue details

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

Nobody has claimed this yet.

Assessment

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

Research direction

Reproduce the flow from a Whimsy report link to the CVE page, then inspect the cveprocess code mentioned in the issue. Check which issue details and project name are transferred; done means the CVE page is populated from an individual report link, or the intended single-link behavior is clearly established.

Written by the indexing model from the issue text.

Description

I tried clicking one of the Whimsy reports to allocate a CVE.
However, the details in the link don’t get transferred to the CVE page; even the project name has to be selected.

This may be an issue with the cveprocess code.
If it is not possible to forward the information, I wonder if individual links are necessary - maybe just have a single link?

Dominant language
JavaScript
Stars
0
Forks
6
Avg merge
1d 7h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

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.

More from apache/security-dash

All issues in apache/security-dash

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.