Skip to content

Releases: aboutcode-org/vulnerablecode

v31.1.0

02 Jan 14:34
40a3974

Choose a tag to compare

What's Changed

Full Changelog: v31.0.0...v31.1.0

v31.0.0

28 Nov 21:37

Choose a tag to compare

This is a major new release with data changes that are API breaking: The way we store CVSS scores has changed.
There is a major new feature with Vulntotal which is like https://www.virustotal.com/ for comparing vulnerability databases. We also re-enabled PostgreSQL advisory imports.

What's Changed

New Contributors

Full Changelog: v30.3.1...v31.0.0

v30.3.1

09 Nov 11:01
0a0460b

Choose a tag to compare

This is a minor bug fix release.

  • We enabled proper CSRF configuration for deployments
  • We improved the content of API key request emails

What's Changed

Full Changelog: v30.3.0...v30.3.1

v30.3.0

08 Nov 23:02
d4d2672

Choose a tag to compare

This is a feature update release including minor bug fixes and the introduction of API keys and API throttling.

What's Changed

Full Changelog: v30.2.1...v30.3.0

v30.2.0

20 Oct 16:32
0e4d61f

Choose a tag to compare

This is a critical bug fix release including features updates.

  • We fixed critical performance issues that made the web UI unusable. This include
    removing some less interesting redundant details displayed in the web UI for
    vulnerabilities.
  • We made minor documentation updates.
  • We re-enabled support for Arch linux, Debian, and Ubuntu security advisories importers
  • We added a new improver for Oval data sources
  • We improved Alpine linux and Gitlab security advisories importers

The summary of performance improvements include these fixes:

  • Cascade queries from exact to approximate searches to avoid full table scans
    in all cases. This is a band-aid for now. The proper solution will likely
    require using full text search instead.
  • Avoid iceberg queries with "prefetch related" to limit the number of queries
    that are needed in the UI
  • Do not recreate querysets from scratch but instead allow these to be chained
    for simpler and correct code.
  • Remove extra details from the vulnerability pacge: each package was further
    listing its related vulnerabilities creating an iceberg query.
  • Enable the django-debug-toolbar with a setting to easily profile queries on demand
    by setting both VULNERABLECODE_DEBUG and VULNERABLECODE_DEBUG_TOOLBAR enviroment
    variables.

What's Changed

Full Changelog: v30.1.1...v30.2.0

v30.1.1

17 Oct 10:04
ac9677b

Choose a tag to compare

What's Changed

Full Changelog: v30.1.0...v30.1.1

v30.1.0

17 Oct 10:00
013ba1d

Choose a tag to compare

What's Changed

Full Changelog: v30.0.0...v30.1.0

v30.0.0

03 Oct 11:20

Choose a tag to compare

Version v30.0.0

This is a major version that is not backward compatible.

  • We refactored the core processing with Importers that import data and Improvers that
    transform imported data and convert that in Vulnerabilities and Packages. Improvers can
    also improve and refine imported and existing data as well as enrich data using external
    data sources. The migration to this new architecture is under way and not all importers
    are available.

    Because of these extensive changes, it is not possible to migrate existing imported
    data to the new schema. You will need instead to restart imports from an empty database
    or access the new public.vulnerablecode.io live instance. We also provide a database dump.

  • You can track the progress of this refactoring in this issue:
    #597

  • We added new data sources including PYSEC, GitHub and GitLab.

  • We improved the documentation including adding development examples for importers and improvers.

  • We removed the ability to edit relationships from the UI. The UI is now read-only.

  • We replace the web UI with a brand new UI based on the same overall look and feel as ScanCode.io.

  • We added support for NixOS as a Linux deployment target.

  • The aliases of a vulnerabily are reported in the API vulnerabilities/ endpoint

  • There are breaking Changes at API level with changes in the data structure:

    • in the /api/vulnerabilities/ endpoint:

      • Rename resolved_packages to fixed_packages
      • Rename unresolved_packages to affected_packages
      • Rename url to reference_url in the reference list
      • Add is_vulnerable property in fixed and affected_packages.
    • in the /api/packages/ endpoint:

      • Rename unresolved_vulnerabilities to affected_by_vulnerabilities
      • Rename resolved_vulnerabilities to fixing_vulnerabilities
      • Rename url to reference_url in the reference list
      • Add new attribute is_resolved
      • Add namespace filter
  • We have provided backward compatibility for url and unresolved_vulnerabilities for now.
    These will be removed in the next major version and should be considered as deprecated.

  • There is a new experimental cpe/ API endpoint to lookup for vulnerabilities by CPE and
    another aliases/ endpoint to lookup for vulnerabilities by aliases. These two endpoints will be
    replaced by query parameters on the main vulnerabilities/ endpoint when stabilized.

  • Added filters for vulnerabilities endpoint to get fixed packages in accordance
    to the details given in filters: For example, when you call the endpoint this way
    /api/vulnerabilities?type=pypi&namespace=foo&name=bar, you will receive only
    fixed versioned purls of the type pypi, namespace foo and name bar.

  • Package endpoint will give fixed packages of only those that
    matches type, name, namespace, subpath and qualifiers of the package queried.

  • Paginated initial listings to display a small number of records
    and provided page per size with a maximum limit of 100 records per page.

  • Add fixed packages in vulnerabilities details in packages endpoint.

  • Add bulk search support for CPEs.

  • Add authentication for REST API endpoint.
    The autentication is disabled by default and can be enabled using the
    VULNERABLECODEIO_REQUIRE_AUTHENTICATION settings.
    When enabled, users have to authenticate using
    their API Key in the REST API.
    Users can be created using the Django "createsuperuser" management command.

  • The data license is now CC-BY-SA-4.0 as this is the highest common
    denominator license among all the data sources we collect and aggregate.

Other:

  • We dropped calver to use a plain semver.
  • We adopted vers and the new univers library to handle version ranges.

What's Changed

Read more

v30.0.0rc6

27 Sep 20:51
3856f05

Choose a tag to compare

What's Changed

Full Changelog: v30.0.0rc5...v30.0.0rc6

v30.0.0rc5

27 Sep 20:51
6688cb6

Choose a tag to compare

What's Changed

Full Changelog: v30.0.0rc4...v30.0.0rc5