Skip to content

affected_version_range should be optional #628

Closed
@Hritik14

Description

@Hritik14

Not all data sources provide an affected version range, there could only be a fixed version. This should be made optional with None as default
https://github.com/nexB/vulnerablecode/blob/283ef0d8878b953b88fb12043b962ab6c59bbb22/vulnerabilities/importer.py#L116-L125

Subsequently, the following needs to be fixed for NoneType
https://github.com/nexB/vulnerablecode/blob/283ef0d8878b953b88fb12043b962ab6c59bbb22/vulnerabilities/importer.py#L130-L136

Reported-By: Tushar Goel <tushar.goel.dav@gmail.com>

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions