Check report Wipe Greeter v1.0.0
What an automated read of this exact file found. It is a list of facts about the code, not a safety verdict. Read it, then read the config, then test on a throwaway server.
Compile check
Compiled on the live game box against Rust build 25670169 (game files dated 2026-10-02, Carbon files dated 2026-10-01), 2026-10-02 (6 days ago). "Without shims" means the plugin does not lean on Carbon's compatibility layer for APIs the game has removed, which is the version most likely to keep working after the next Rust update and to run on Oxide.
WipeGreeter.cs
- With Carbon's shims: compiles
- Without shims: compiles
No hot-path hooks registered.
SHA-256 of this file
57a36b59d0487b2d88fc6c859797f3224cea4dfb896c3671b3cd487a5900b725
Hooks it registers 3
Findings 0
Nothing in the categories checked: no network calls, no processes, no dynamic loading, no encoded blobs, no writes outside the plugin's own paths, no hardcoded Steam IDs, no Harmony patches.
What was checked
Outbound network use and URLs, Discord webhooks, process and shell use, native imports, dynamic assembly loading and code generation, unsafe blocks, Base64 decoding and long encoded literals, file writes and deletes, server config and RCON references, hardcoded Steam IDs, admin flag changes, Harmony patches, console commands and server stops, repeating timers, config writes, and the hook names registered. The compile check above builds the file on the live game box against the current Rust and Carbon files, publicized the way Carbon does at boot, with Carbon's compat shims and without them. Not checked: whether the logic is correct or kind, or whether the config it ships with points anywhere.
