Most of what the author discovered is real and technically correct, but it is also undocumented, unsupported, and risky to rely on.
GitHub has changed node ID internals before, quietly. If they add a field to the MessagePack array, switch encodings, encrypt payloads, introduce UUID-backed IDs..
every system relying on this will break instantly.
I fired up a 5$ Hetzner server, and then scanned 10k+ wordpress plugins for security issues, errors, warnings etc using .. it took around 5 days to complete..
Under the hood, it uses the official Plugin Check (via wp plugin check) and PHP_CodeSniffer with the WordPress standards, plus some extra checks for plugin repo requirements and performance. So its basically the plugin check but with a web interface. There are some false positives in the scan results but it gives an overall picture about a plugin.
GitHub has changed node ID internals before, quietly. If they add a field to the MessagePack array, switch encodings, encrypt payloads, introduce UUID-backed IDs..
every system relying on this will break instantly.
reply