VulCode

Proxmox VE: our changes to an open source project

A server virtualisation platform with KVM machines and LXC containers, managed from the browser. It takes fixes through the pve-devel mailing list rather than pull requests.

All contributions
Proxmox VE
git.proxmox.com
Language
Perl and JavaScript
Repositories
pve-manager, proxmox-widget-toolkit
Project site
proxmox.com
6patches applied by the maintainers
From 26 Sep 2026 to 29 Sep 2026.

Every change merged into Proxmox VE

Newest first, as written on git.proxmox.com. Next to the date is the short hash of the commit a maintainer applied; the row opens it.

Patches through pve-devel, not pull requests

Proxmox does not take pull requests. Patches go by email to pve-devel after signing a contributor licence agreement, and a maintainer applies them to the repository.

What it taught us

In a large infrastructure project the interface must validate data the same way the API does, or users only learn about an error after submitting. We also learned to work through a mailing list: a patch has to stand on its own, without a comment thread to explain it.

  1. A Bugzilla report

    A numbered bug described by users. Our patches answer these reports:

    • #64751 patch
    • #71081 patch
    • #80152 patches
    • #56081 patch
    • #69431 patch
  2. A patch via git send-email

    To the pve-devel list, explained in the email. From us: 6 patches.

  3. Review on the list

    Review and testing by the project's maintainers, on the same list.

Proxmox VE among all our changes

Day by day from 5 September 2026 to 11 October 2026. A column is every change merged that day, the accent is the changes in Proxmox VE.

  • Changes in Proxmox VE
  • Changes in other projects

6 merged changes in Proxmox VE

The first on 26 September 2026, the latest on 29 September 2026.

On the same days

Changes of ours were also merged into: compromise, python-benedict.

The whole period

125 merged changes in 65 projects.

Questions about our changes to Proxmox VE

Where these changes come from, who merged them and whether we can fix something in your library.

Using Proxmox VE in your project?

If something in it does not work, we fix it at the source and leave a workaround until the release. We reply within an hour.