You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other than the fields that are already there in the report like the dependency ChangeType, AggregateScore, PackageName, Version, we might want to add some links for users to refer to.
For example, for those with a valid source repo URI, we can add a markdown hyperlink to the dependency's src repo. @laurentsimon is also suggesting adding deps.dev pages to these dependencies, but we haven't found a reliable answer on which deps.dev page we should give for each dependency.
For example, for those with a valid source repo URI, we can add a markdown hyperlink to the dependency's src repo. @laurentsimon is also suggesting adding deps.dev pages to these dependencies, but we haven't found a reliable answer on which deps.dev page we should give for each dependency.
I thought we would ask folks at deps.dev about that?
For example, for those with a valid source repo URI, we can add a markdown hyperlink to the dependency's src repo. @laurentsimon is also suggesting adding deps.dev pages to these dependencies, but we haven't found a reliable answer on which deps.dev page we should give for each dependency.
I thought we would ask folks at deps.dev about that?
I'll send an email to the deps.dev team to ask about it
Please see an output example here.
Other than the fields that are already there in the report like the dependency
ChangeType
,AggregateScore
,PackageName
,Version
, we might want to add some links for users to refer to.For example, for those with a valid source repo URI, we can add a markdown hyperlink to the dependency's src repo. @laurentsimon is also suggesting adding deps.dev pages to these dependencies, but we haven't found a reliable answer on which deps.dev page we should give for each dependency.
There could be other options, we'd love to hear about more new ideas ;-)
@azeemshaikh38 @naveensrinivasan
The text was updated successfully, but these errors were encountered: