Navigation

    Inedo Community Forums

    Forums

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. caterina
    3. Topics
    C
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by caterina

    • C

      ProGet 2023.13: Delay after package upload
      Support • • caterina  

      3
      0
      Votes
      3
      Posts
      18
      Views

      C

      Hi @Dan_Woolf, so it seems to be a long known issue: https://github.com/NuGet/Home/issues/3116 Thank you for your help. Caterina
    • C

      pgscan: lockfileVersion 3 for npm dependencies not supported
      Support • • caterina  

      16
      0
      Votes
      16
      Posts
      55
      Views

      gdivis

      Thanks! Merged and released.
    • C

      ProGet: Vulnerability assessment types - missing vulnerabilities
      Support • • caterina  

      2
      0
      Votes
      2
      Posts
      13
      Views

      rhessinger

      Hello, This is most likely related to PG-2395 (ProGet 2022.30 fix) and PG-2390 (ProGet 2023.9 fix). We added support to handle when OSS Index removes vulnerabilities from their list. Unfortunately, this has brought to light the unreliability of the data returned from OSS Index. It looks like vulnerabilities are constantly removed and re-added, which caused assessments to be cleared out on vulnerabilities. In PG-2395 and PG-2390, we have updated ProGet to only add a comment if we see that OSS Index deleted it. This way the assessment is not lost when OSS Index removes the vulnerability. Thanks, Rich
    • C

      Wrong version shown in Usage&Statistics
      Support • • caterina  

      2
      0
      Votes
      2
      Posts
      13
      Views

      stevedennis

      Hi @caterina , This behavior is intentional, but not ideal. It should only navigation - such as the "Usage & Statics" page on a package, or the "List Projects" page which has a "Latest Release" column. As long as the Release is active, you'll still see new issues come up. That's really what determines if a release is scanned or not - Active or not. The reason for this... an SCA Release's "Release Number" is a free-form field, which means there are no sorting rules. So we can't practically/easily determine what the "highest" number. Instead, we just use the order in which it was created for display purposes. Thanks, Steve
    • 1
    • 2
    • 2 / 2