discord-backup
📦 Complete framework to facilitate server backup using discord.js v13
Runs with mockssource: GitHubhomepageTypeScriptMITcommit 472cb7c8eb3d
TypeScript, MIT licensed. The project labels itself: backup, clone, discord, framework and server.
discord-backup runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
discord-backup v3.4.0 installs, builds, and lints cleanly; file-based backup storage operations (setStorageFolder, list, fetch, remove) and security validation work correctly; Discord-dependent create/load functions require a real Discord bot token and guild to test.
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 86 of 100 (the mean of this project's run scores).
At a glance
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
- under a minute
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- npm run build exited 0, npm run lint exited 0; node test script confirmed list/fetch/remove/setStorageFolder all work correctly (LIST PASS, FETCH id=TEST123 size=0.44kb, REMOVE file deleted, SECURITY path traversal blocked)
- Model tokens used
- 72,797
- Exact commit tested
- 472cb7c8eb3d
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
All done. Let me compile the final report.
Here's what I verified:
**Install** (`npm install` + `npm run build`): succeeded — 87 packages installed, TypeScript compil…
**Lint** (`npm run lint`): passed with zero errors.
**API surface**: all 6 public functions (`create`, `fetch`, `load`, `remove`, `list`, `setStorageFo…
**File-based operations verified end-to-end:**
- `setStorageFolder()` + `list()` on empty storage returns `[]`
- Manually writing a valid backup JSON to storage, then `list()` returns it, `fetch()` returns corr…
- `remove()` deletes the file and subsequent `fetch()` correctly rejects with "No backup found"
- Path traversal attacks blocked — `fetch('../etc/passwd')` rejects with "Invalid backup ID"
**Discord-dependent functions** (`create`, `load`) require a real Discord bot token and guild — no …
`ARGUSIC_RESULT:`**`{"install_succeeded":true,"launch_succeeded":true,"install_minutes":0.5,"errors…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 0.5 minutes, faster than the median of the 47 comparable projects Argusic has measured.
- 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
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Of the 48 backup projects Argusic has installed and timed, discord-backup was the 8th fastest to reach a running state, and 32 of 48 reached one at all.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.01 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.01 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/discord-backup)Questions
- Does discord-backup run?
- discord-backup runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test discord-backup?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 472cb7c8eb3d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test discord-backup?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does discord-backup take to install?
- 0.5 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 discord-backup need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing discord-backup?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does discord-backup compare with the alternatives?
- Of the 48 backup projects Argusic has installed and timed, discord-backup was the 8th fastest to reach a running state, and 32 of 48 reached one at all.
- Where is the evidence for discord-backup?
- 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.