DPP

C++ Discord API Bot Library - D++ is Lightweight and scalable for small and huge bots!

Not yet verifiedsource: GitHubhomepageC++Apache-2.0commit 786ceb2e24f2

C++, Apache-2.0 licensed. The project labels itself: api, api client, api wrapper, cpp, discord, discord api, discord api v10 and discord api wrapper.

DPP has not been verified yet.

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

At a glance

verdict
Not yet verified
Argusic Score
80 / 100
recorded runs
1
last tested
stars
1,398
forks
210
open issues
4
watchers
21
size
57 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 most recent recorded attempt, which did not reach a verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing DPP, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Missing zlib development headers and library symlink2 minutes
Install time
7 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
cd /work/repo/build/library && LD_LIBRARY_PATH=/work/repo/build/library ./unittest -- exited 0, 64 passed, 0 failed, 108 skipped (offline mode)
Model tokens used
47,775
Exact commit tested
786ceb2e24f2
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.

D++ 10.1.7 (06-Aug-2026)
Voice support not enabled in this build of D++
All tests passed. Let me compile the final report.
Here's the summary of everything I did:
**Build**: Configured with CMake (`-DDPP_NO_VCPKG=ON -DDPP_NO_CONAN=ON -DBUILD_VOICE_SUPPORT=OFF`),…
**Tests**: Ran the `unittest` binary. 64 offline tests passed, 108 online tests skipped (no Discord…
tokens used
47,775
All tests passed. Let me compile the final report.
Here's the summary of everything I did:
**Build**: Configured with CMake (`-DDPP_NO_VCPKG=ON -DDPP_NO_CONAN=ON -DBUILD_VOICE_SUPPORT=OFF`),…
**Tests**: Ran the `unittest` binary. 64 offline tests passed, 108 online tests skipped (no Discord…

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.

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 Runner1/3Unverified80.000.03

Topics (from GitHub)

apiapi-clientapi-wrappercppdiscorddiscord-apidiscord-api-v10discord-api-wrapperdiscord-botdockerdppetfhacktoberfestjsonlibrarylinuxosxsslwebsocketwindows

Embed the badge

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

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

Questions

Does DPP run?
DPP has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test DPP?
On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
Where is the evidence for DPP?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion