Tushar Goel

This is done now! PRs for references: https://github.com/aboutcode-org/vulnerablecode/pull/1701 https://github.com/aboutcode-org/vulnerablecode/pull/1631 https://github.com/aboutcode-org/vulnerablecode/pull/1558 To test this We have a new endpoint deployed and live on https://public.vulnerablecode.io/api/v2/ /api/v2/vulnerabilities- https://public.vulnerablecode.io/api/v2/vulnerabilties Vulnerabilities endpoint- This endpoint has...

@nnobelis please try https://pypi.org/project/python-inspector/0.9.5/ and let us know if this fixes the above issue.

@NucleonGodX a gentle reminder, is this PR active ?

- Add source URL for all advisories, Importer ID - Added Source URL - Add date published for the advisory - Done - Use Vulneribilities instead of Advisories, keep Advisory...

This is done now! PRs for references: - https://github.com/aboutcode-org/vulnerablecode/pull/1866 To test this: Set up Vulnerablecode on your system locally and run a new V2 importer pipeline for example: ./manage.py import...

We should have severity on vulnerability and package-vulnerability relationship if we don't have severity on the package-vulnerability relationship then we should use only the vulnerability severity.

- Start with tests to see what's breaking - Refactor VulnerabilitySeverity models, disassociate severity from reference. And attach severity on vulnerability and package-vulnerability relationship

Blocked by this https://github.com/aboutcode-org/vulnerablecode/pull/1612

@pombredanne do let me know which way makes best sense, or if you have any other way in mind, let me know

- Waiting for merging of https://github.com/nexB/vulnerablecode/pull/1310