Advertisement

Proxmox Helper Scripts: Where They Live Now and How to Check One

By the Softwares Academy editors Updated Checked against official sources on 26 Sep 2026

Short answer: The Proxmox helper scripts (officially “Proxmox VE Helper-Scripts”) now live at github.com/community-scripts/ProxmoxVE, with the website community-scripts.org. They are a community project under the MIT license, not a Proxmox product. They began as tteck’s scripts. tteck announced on October 29, 2024 that he had entered hospice care, and his original repository was archived on November 2, 2024. The community edition continues “in memory of tteck.” Each script runs as root on your Proxmox host and downloads more code while it runs, so read it, and the files it pulls in, before you pipe it to bash.

Where the Proxmox helper scripts live now

Address What it is
github.com/community-scripts/ProxmoxVE The active repository. Created November 1, 2024. MIT license
community-scripts.org The project website, listed as the repository’s homepage. Each script page shows its install command
github.com/community-scripts/ProxmoxVED Where new scripts are tested before they reach the main repository
github.com/tteck/Proxmox The original repository. Archived and read-only

The old addresses redirect. On September 26, 2026, community-scripts.github.io/ProxmoxVE redirected to community-scripts.org, and tteck’s old site, helper-scripts.com, redirected to a community-scripts page on GitHub Pages.

The README calls the project “One-command installations for services, containers, and VMs on Proxmox VE.” It lists requirements of Proxmox VE 8.4, 9.0, 9.1 or 9.2, root shell access on the host, and an internet connection during installation.

Advertisement

What happened to tteck

tteck wrote the original Proxmox VE Helper-Scripts. On October 29, 2024, he posted in the project’s GitHub discussions that he had “transitioned into hospice care” and would slow development. A later edit to that post said he had been diagnosed with incurable cancer. The original repository was archived on November 2, 2024. Its README now points to the new home at github.com/community-scripts/ProxmoxVE.

The community edition says it is “built on the foundation of @tteck’s original work” and is “Maintained and expanded by the community · In memory of tteck.” It also says 30% of donations go to cancer research and hospice care.

How a helper script runs

Each script page on community-scripts.org gives a one-line command. For the Debian container, it is:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)"

That line downloads ct/debian.sh from GitHub and runs it immediately, as root, on your Proxmox host. The script you see is not the whole script. When we read ct/debian.sh on September 26, 2026, its first lines loaded a shared file, build.func, from a second repository, community-scripts/core, which was created on August 5, 2026. build.func builds the container. A separate install script then runs inside the new container.

tteck’s original CODE-AUDIT file describes the same chain for an AdGuard container: the app script collects settings, build.func adds your choices, create_lxc.sh builds the container, and adguard-install.sh installs the app. It says to focus on the app’s install script, because that holds the commands that install and configure the software.

The Debian script’s defaults, read from the file, are 1 CPU core, 512 MB of RAM, a 2 GB disk, Debian 13 and an unprivileged container. Advanced mode lets you change them.

How to review a script before you pipe it to bash

  1. Download it to a file instead of running it. 
    curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh -o debian.sh
less debian.sh
  2. Find everything else it fetches. Search for curl, wget and source. Every URL you find is more code that will run. For container scripts, that includes build.func from community-scripts/core and the matching file in the install/ folder. 
    grep -nE 'curl|wget|source' debian.sh
  3. Read the install script. It’s the part that installs packages, adds repositories and opens ports. Check where each package comes from.
  4. Check the history. On GitHub, open the file’s history and look at recent commits. A sudden change from an unfamiliar account deserves a closer look.
  5. Remember that main moves. The command always fetches the newest version from the main branch, and the shared build.func is fetched at run time too. What you reviewed yesterday may not be what runs today. Review on the day you run it.
  6. Test first. Run it on a test node, or back up your host configuration and guests before running it on a server you care about.

Risks to weigh

  • Root on the host. The scripts need root shell access on the Proxmox host, as the README says. A mistake or a malicious change could affect every guest on that host.
  • Runtime downloads. The scripts fetch code from GitHub while they run. If GitHub or the repository were compromised, the command would run whatever was there.
  • Not from Proxmox. The project is run by volunteers. Its README says “Proxmox® is a registered trademark of Proxmox Server Solutions GmbH.” When a user asked on the Proxmox forum about patching Proxmox VE to remove its subscription notice, a Proxmox staff member replied that any such modification is “not supported and you are on your own.” That answer was about patching Proxmox itself, but it shows the line Proxmox draws: changes from outside its own packages are your responsibility.
  • Third-party app sources. Each install script pulls the app itself from its own upstream source. Your trust extends to every one of those.
  • Copies and forks. Only use the command shown on community-scripts.org or in the community-scripts GitHub repository. Forks and reposts may be out of date or changed. We haven’t seen a lookalike domain named by the project, so we don’t list one.

How the project handles security reports

The repository’s security policy asks people not to report vulnerabilities publicly. Reports go by direct message to a maintainer on Discord or by email to [email protected]. The policy says maintainers will acknowledge a report within 7 business days. It lists Proxmox VE 8.4.x through 9.2.x as supported, and 8.0.x to 8.3.x with limited support.

When to skip the scripts

  • You’re learning Proxmox and want to understand containers. Creating one yourself from a Proxmox template teaches more. Our Proxmox VE install guide covers the built-in templates.
  • The host runs production workloads with a support subscription. Keep changes to what Proxmox documents.
  • You can’t spare the time to read the script. Then don’t run it.

Proxmox VE itself is free. See is Proxmox free? for what a subscription adds, and our Proxmox VE app page for the current ISO and its SHA-256 hash. For a general checklist on scripts and downloads from unofficial places, see our guide to fake download sites.

Questions

What is the official site for Proxmox helper scripts?

community-scripts.org, and the GitHub repository github.com/community-scripts/ProxmoxVE.

Are the helper scripts made by Proxmox?

No. They’re a community project. Proxmox Server Solutions GmbH makes Proxmox VE.

Is tteck still maintaining the scripts?

No. tteck announced on October 29, 2024 that he had entered hospice care. The community took over, and the project continues in his memory.

Is helper-scripts.com still the site?

No. It now redirects to a community-scripts page. Use community-scripts.org.

Are Proxmox helper scripts safe?

They’re open source and publicly reviewed, but they run as root and download code at run time. Read each script and the files it loads before you run it.

Why doesn’t reading the main script show everything?

Container scripts load a shared build.func from the community-scripts/core repository and run a separate install script inside the container.

Which Proxmox versions do the scripts support?

The README lists Proxmox VE 8.4, 9.0, 9.1 and 9.2.

What license are the scripts under?

MIT.

Where do I report a security problem in a script?

Privately, by Discord direct message to a maintainer or by email to [email protected], as the security policy says.

Sources