When we display package manifest and lock files, hyperlink to the upstream package repo web page

[pombredanne]

When we display a package manifest or lockfile in the resource details, we should have a way to add a hyperlink to the upstream repository web page for this repo: for instance when we browse a requirements.txt lockfile, if it contains: scancode-toolkit==30.0.1 we should recognize this and link to https://pypi.org/project/scancode-toolkit/30.1.0/

We can parse manifests alright and we can create URLs based on the ScanCode TK packagedcode classes.

[soma2000-lang]

@pombredanne can I work on this

[pombredanne]

@soma2000-lang sure thing. If you do, I think starting with requirements.txt files would be great. Another easy one would be go.mod and go.sum

[soma2000-lang]

Ok

[the-illuminatus]

@pombredanne is this issue unresolved?. I would love to work on it in case it is before mentioned.

[pombredanne]

@the-illuminatus I have not heard back from Soma and there has been no pending PRs... so go for it!
Note that you can likely reuse the URL templates and functions to get the proper URL that exist in scancode-toolkit packagedcode code. See https://github.com/nexB/scancode-toolkit/blob/fff140efd68dd0098f09ad1bc675569f1f1ad6ae/src/packagedcode/pypi.py#L1163

[the-illuminatus]

Sure, thanks!

…

On Sun, 10 Apr 2022, 10:19 pm Philippe Ombredanne, ***@***.***> wrote: @the-illuminatus <https://github.com/the-illuminatus> I have not heard back from Soma and there has been no pending PRs... so go for it! Note that you can likely reuse the URL templates and functions to get the proper URL that exist in scancode-toolkit packagedcode code. See https://github.com/nexB/scancode-toolkit/blob/fff140efd68dd0098f09ad1bc675569f1f1ad6ae/src/packagedcode/pypi.py#L1163 — Reply to this email directly, view it on GitHub <#403 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASKNS5G4GWQZJ3NACQTFQVLVEMBCNANCNFSM5PIPHJTQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[pombredanne]

A good example of a similar UI would be the hyperlinking in this https://gitlab.com/gitlab-org/security-products/analyzers/gemnasium/-/blob/master/Gemfile ... or https://gitlab.com/gitlab-org/security-products/analyzers/gemnasium-python/-/blob/v2/requirements.txt
In the SCIO UI, when we look a Codebase Resource content and that's a manifest file, we should get the URLs collected from SCTK or just use a few heuristics to hyperlink to the public package repo

[the-illuminatus]

Sure will look into it.

…

On Mon, 25 Jul 2022, 9:58 pm Philippe Ombredanne, ***@***.***> wrote: A good example of a similar UI would be the hyperlinking in this https://gitlab.com/gitlab-org/security-products/analyzers/gemnasium/-/blob/master/Gemfile ... or https://gitlab.com/gitlab-org/security-products/analyzers/gemnasium-python/-/blob/v2/requirements.txt In the SCIO UI, when we look a Codebase Resource content and that's a manifest file, we should get the URLs collected from SCTK or just use a few heuristics to hyperlink to the public package repo — Reply to this email directly, view it on GitHub <#403 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASKNS5D5UQCBDFDLSBRHAV3VV26CFANCNFSM5PIPHJTQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[pombredanne]

@the-illuminatus Thanks! note also that @lf32 was interested in fixing it.

[35C4n0r]

@pombredanne is this issue still open?

[lf32]

Yes, It's open

[melencholicmice]

@lf32 @pombredanne
is this issue still open? I would like to look into in.