Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add missing OSV schema fields to vulnerability page #2132

Merged
merged 11 commits into from
May 23, 2024
Merged

Add missing OSV schema fields to vulnerability page #2132

merged 11 commits into from
May 23, 2024

Commits on May 20, 2024

  1. Fix the indentation

    @zahraaalizadeh
    zahraaalizadeh committed May 20, 2024
    Configuration menu
    Copy the full SHA
    a909518 View commit details
    Browse the repository at this point in the history

  2. Display purl info on the vulnerability page

    @zahraaalizadeh
    zahraaalizadeh committed May 20, 2024
    Configuration menu
    Copy the full SHA
    b88f6d7 View commit details
    Browse the repository at this point in the history

  3. Add severity details to the vulnerability page

    @zahraaalizadeh
    zahraaalizadeh committed May 20, 2024
    Configuration menu
    Copy the full SHA
    040c81c View commit details
    Browse the repository at this point in the history

  4. Add the credits info to the vulnerability page

    @zahraaalizadeh
    zahraaalizadeh committed May 20, 2024
    Configuration menu
    Copy the full SHA
    c56092e View commit details
    Browse the repository at this point in the history

  5. Remove duplicated if statement 

    Earlier in the html, there is a duplicated `if` statement
to display the pacjange if it existed in the affected
payload.

This change removes the duplicated `if` statement in favour
of the parent `if` statement.
    @zahraaalizadeh
    zahraaalizadeh committed May 20, 2024
    Configuration menu
    Copy the full SHA
    d27dfd7 View commit details
    Browse the repository at this point in the history

  6. Expose severity per affected if any

    @zahraaalizadeh
    zahraaalizadeh committed May 20, 2024
    Configuration menu
    Copy the full SHA
    855e39b View commit details
    Browse the repository at this point in the history

  7. Fix the link to affected database specific 

    Priorly, affected database specific was linked to
affected range database specific.

This change updates the link to point to the correct address.
    @zahraaalizadeh
    zahraaalizadeh committed May 20, 2024
    Configuration menu
    Copy the full SHA
    4f2c775 View commit details
    Browse the repository at this point in the history

  8. Expose affected range database specific info

    @zahraaalizadeh
    zahraaalizadeh committed May 20, 2024
    Configuration menu
    Copy the full SHA
    40c7572 View commit details
    Browse the repository at this point in the history

  9. Add a space before dash for credit

    @zahraaalizadeh
    zahraaalizadeh committed May 20, 2024
    Configuration menu
    Copy the full SHA
    2fcd956 View commit details
    Browse the repository at this point in the history

  10. Add missing space

    @zahraaalizadeh
    zahraaalizadeh committed May 20, 2024
    Configuration menu
    Copy the full SHA
    a7afa62 View commit details
    Browse the repository at this point in the history

  11. Make the rendering of severity consistent

    @zahraaalizadeh
    zahraaalizadeh committed May 20, 2024
    Configuration menu
    Copy the full SHA
    db8349b View commit details
    Browse the repository at this point in the history