ProxmoxVE

Proxmox VE Helper-Scripts (Community Edition)

Could not verifysource: GitHubhomepageShellMITcommit ac446889250b

Shell, MIT licensed. The project labels itself: alpine, authentification, container, debian, docker, home assistant, home automation and homelab.

Argusic could not get ProxmoxVE running. An Argusic agent installed it in 10 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

All 1304 shell scripts and 10 core .func library files pass syntax validation; core libraries (core.func, api.func, error_handler.func, build.func) load and execute correctly with all functions defined; the repository cannot run end-to-end without a Proxmox VE host, but every script in the repo is syntactically valid.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 65 of 100 (the mean of this project's run scores).

At a glance

verdict
Could not verify
Argusic Score
65 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
2
last tested
stars
29,661
forks
2,903
open issues
21
watchers
121
size
44 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
10 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
bash -n on all 1304 .sh and 10 .func files passed with zero failures; core libraries sourced and msg_info/msg_ok/variables/build_container functions verified working; ShellCheck on misc/core.func misc/install.func misc/error_handler.func misc/api.func misc/build.func misc/tools.func misc/vm-core.func misc/cloud-init.func misc/alpine-install.func misc/alpine-tools.func found no errors (only style/info/warnings); .github/workflows/scripts/generate-app-headers.sh also validated
Model tokens used
132,916
Exact commit tested
ac446889250b
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Whether it works at all
this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

# License: MIT | https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/LICENSE
set -euo pipefail
SPINNER_PID=""
      stop_spinner
      msg_ok "Fetched: $url"
      $has_output_file || printf '%s' "$result"
      return 0
    fi
All verification is complete. Here's a summary of the findings.
tokens used
132,916
All verification is complete. Here's a summary of the findings.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 10 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • An agent with no time limit did not get it running.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Unverified80.000.03
Argusic Runner1/3Did not run50.000.05

Topics (from GitHub)

alpineauthentificationcontainerdebiandockerhome-assistanthome-automationhomelabhomelab-setuplxcnetworkproxmoxproxmox-vescriptssecurityself-hostedself-hostingsmarthomeubuntuvm

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/ProxmoxVE.svg)](https://argusic.com/subject/proxmoxve)

Questions

Does ProxmoxVE run?
Argusic could not verify that ProxmoxVE runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test ProxmoxVE?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ac446889250b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test ProxmoxVE?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ProxmoxVE take to install?
10 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does ProxmoxVE need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ProxmoxVE?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for ProxmoxVE?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion