Yes. The Palette Manager only displays the two types of modules that can be installed via NR. It's either a node, a plugin, or both. The sidebar can be registered by either a node or a plugin. It's not possible any other way.
Your tarball module doesn't contain a plugin entry in the package.json file, so NR won't lookup for a plugin. However, NodeDev does have an entry, but since you're not registering a plugin, it considers it to be zero. A plugin file can contain multiple plugins; it's the same principle as for nodes.
Hiding the amount isn't an option because you're skipping the plugin registration. You can use a resource instead if you don't want to register a plugin.
I think the question remains: why do I need to call registerPlugin for something that has a sidebar and is working as a sidebar?
What is the difference between sidebar and plugin?
But that seems to be static content which I'm not loading. I'm loading a sidebar definition which also needs to be executed at startup. Hence the plugin in the package.json - to ensure it gets called.
The plugin concept was introduced to put a bit more structure around modules that wanted to add stuff to the runtime/editor without being associated directly with a node.
It provides a way to have standard 'types' of plugin - such as custom themes.
It is something that needs documentation writing for.
But if what you're doing works, there's no pressure to change.