Skip to content

Vulnerabilities and vulnerability exports API #2316

Closed as not planned
Closed as not planned

Description

@srisaravananwt

Description of the problem, including code/CLI snippet

Need modules for https://docs.gitlab.com/ee/api/vulnerabilities.html and https://docs.gitlab.com/ee/api/vulnerability_exports.html

Expected Behavior

Option to use Vulerabilities and vulnerability_export api.

Actual Behavior

No option to use Vulerabilities and vulnerability_export api.

Specifications

  • python-gitlab version:
  • API version you are using (v3/v4):
  • Gitlab server version (or gitlab.com): 15.x

Activity

  1. nejch commented on Oct 16, 2022

    @nejch
    Member

    Hi @srisaravananwt, thanks for the report. I've added the help wanted label here as this is an Ultimate plan feature.

  2. changed the title [-][Feature Request][/-] [+]Vulnerabilities and vulnerability exports API[/+] on Oct 16, 2022
  3. srisaravananwt commented on Oct 16, 2022

    @srisaravananwt
    Author

    @nejch Thanks. Could you please point me to the similar MR for any other features like this? I will try to contribute.

  4. nejch commented on Oct 16, 2022

    @nejch
    Member

    Awesome! Since vulnerabilities is mostly an instance-level endpoint, (e.g. you will likely do vuln = gl.vulnerabilities.get(vuln_id), I think the closest might be the Topics API, see this commit here: 91cd74d. This should give you a basic idea.

    Now I see it has a lot of custom endpoints for confirm, dismiss, etc. These will be methods on the object itself, not the manager (e.g. vuln.dismiss()). For these, I'd maybe take a look at #2064.

    Also keep in mind I just noticed they are deprecating this REST endpoint in favor of GraphQL. But that will probably take years, so if you need it now it probably makes sense still :)

  5. Rewdog commented on Jan 19, 2023

    @Rewdog

    Hey @srisaravananwt , any work on this? I need this as well and can help out on the fork.

  6. srisaravananwt commented on Jan 20, 2023

    @srisaravananwt
    Author

    @Rewdog I have used GraphQL to export the vulnerability report.

  7. irishismyname commented on Jan 2, 2024

    @irishismyname

    @Rewdog I have used GraphQL to export the vulnerability report.

    I think this is the only way forward, the REST APIs (Vulnerabilities and Vulnerability Findings) are deprecated and have issues (i.e., pagination doesn't currently work).

    That said, pagination is also currently broken in the GraphQL securityReportFindings connection. I'm currently working with their tech support to figure it out.

  8. github-actions commented on Jul 9, 2025

    @github-actions

    This issue was marked stale because it has been open 60 days with
    no activity. Please remove the stale label or comment on this
    issue. Otherwise, it will be closed in 15 days.

    As an open-source project, we rely on community contributions to
    address many of the reported issues. Without a proposed fix or
    active work towards a solution it is our policy to close inactive
    issues. This is documented in CONTRIBUTING.rst

    How to keep this issue open:

    • If you are still experiencing this issue and are willing to
      investigate a fix, please comment and let us know.
    • If you (or someone else) can propose a pull request with a
      solution, that would be fantastic.
    • Any significant update or active discussion indicating progress
      will also prevent closure.

    We value your input. If you can help provide a fix, we'd be happy
    to keep this issue open and support your efforts.

    This is documented in CONTRIBUTING.rst
    https://github.com/python-gitlab/python-gitlab/blob/main/CONTRIBUTING.rst

  9. github-actions commented on Jul 24, 2025

    @github-actions

    This issue was closed because it has been marked stale for 15 days
    with no activity.

    This open-source project relies on community contributions, and
    while we value all feedback, we have a limited capacity to address
    every issue without a clear path forward.

    Currently, this issue hasn't received a proposed fix, and there
    hasn't been recent active discussion indicating someone is planning
    to work on it. To maintain a manageable backlog and focus our
    efforts, we will be closing this issue for now.

    This doesn't mean the issue isn't valid or important. If you or
    anyone else in the community is willing to investigate and propose
    a solution (e.g., by submitting a pull request), please do.

    We believe that those who feel a bug is important enough to fix
    should ideally be part of the solution. Your contributions are
    highly welcome.

    Thank you for your understanding and potential future
    contributions.

    This is documented in CONTRIBUTING.rst
    https://github.com/python-gitlab/python-gitlab/blob/main/CONTRIBUTING.rst

  10. locked as resolved and limited conversation to collaborators on Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    EEIssues related to the enterprise version of GitLabfeaturehelp wantedstale

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions