Two major, well-known WordPress plugins have recently implemented certain changes which have not gone down well with the WordPress community.
Jetpack in version 7.1, made a change with Jetpack active when you go to
/wp-admin/ Plugins > Add New
If a Jetpack module has similar features to the plugin keyword you are searching for, the first result will be the Jetpack module. The Jetpack PR shows the original proof of concept of the plugin suggestion feature. If you already have Jetpack active, then you would use a module which is already available in Jetpack, instead of installing another plugin.
The issue comes from where Automattic, the company behind Jetpack as well as WordPress.com and WordPress.org, seems like it is flaunting the plugin guidelines. If you have Jetpack active, then the plugin search results will be skewed in favor of Jetpack.
You can test two basic plugin keyword searches on optimize and backup. Optimize will show the Asset CDN module in Jetpack as the top result, whilst the plugin keyword search for backup will show VaultPress as the top-suggested plugin result in the plugin keyword search.
One slightly suspect feature is that Jetpack now tracks keyword plugin search terms longer than three characters. This gives Automattic a huge edge other many other companies which are behind WordPress plugins on WordPress.org.
This leaves the door open for what else might be changed in Jetpack to skew or advertise certain services and plugins when the Jetpack plugin is active on a site. Again, the plugin suggestion feature will only show if Jetpack is installed and active on a site. Jetpack put out a maintenance release in version 7.2.1 on the 4th April that made those clearer.
You can use a code snippet on your child site to disable the plugin search suggestions from showing when Jetpack is active.
Yoast SEO Call Home
Even if no add-ons from Yoast are installed and active on the site, the current version of Yoast SEO 10.1.1 will keep on calling home. The call to Yoast will slow the site down where it is active, doing so without permission. The issue in Yoast SEO 10.1.1 was not correctly fixed in 10.1.2, but the issue should be fixed in version 10.1.3.
Plugins, especially ones as highly-installed as Jetpack, which has 5+ million active installs and Yoast SEO which also has 5+ million active installs, need to be clearer on adding features that customers really need, and not ones which end up serving those companies.
WordPress plugins need to clearly communicate any major feature changes as to what calls the plugin makes to an external URL, and for what reason.