I've mentioned this before but I keep seeing it remains unresolved. I must say I don't know how the plugin update system works in OPNsense or who's responsible for this work. As of today, the dnscrypt plugin in OPNsense works with version 2.1.5, but I'm seeing version discrepancies across different sources.
In the OPNsense plugin repository, it has version 1.15 integrating dnscrypt-proxy 2.1
https://github.com/opnsense/plugins/blob/master/dns/dnscrypt-proxy/pkg-descr
In the FreeBSD repositories, dnscrypt has version 2.1.5_13 updated on June 6, 2025.
https://www.freshports.org/dns/dnscrypt-proxy2/
And on the official Dnscrypt website on GitHub, they're already at version 2.1.12, which is what OPNsense should have.
https://github.com/DNSCrypt/dnscrypt-proxy/releases/tag/2.1.12
The funny thing is that on dnscrypt's GitHub, the program is available for FreeBSD, so it would be appreciated if it could be updated either on FreeBSD or directly on Opnsense.
Any upstream project like DNScrypt release at their own pace.
Any FreeBSD port/package of such an upstream project has a port maintainer responsible for the port. People do this as volunteer work and in their spare time so some less important ports might be significantly behind their upstream version. The important infrastructure ones (PHP, MariaDB, ...) are usually updated instantly.
Anyone can submit a patch in the FreeBSD bug tracker to bring a port up to date.
The OPNsense project uses the FreeBSD project as its upstream, so changes in FreeBSD most of the time need to happen first, before OPNsense can incorporate them. Sometimes the OPNsense team sees the need to fix some problem in FreeBSD faster and in turn creates a bug entry with patches in the FreeBSD bug tracker.
Hope that explains it. There is no single person "not doing their job". All of this is open source and anyone can update the package and submit the changes if they deem that important.