It's not supposed to, and this seems to be an unwanted side-effect of the new version requesting "tabs" permission (i.e. access to the current tabs). That's only used to check whether the Bookmark Manager is currently active, so SuperSorter can hold off sorting if the user is actively editing their bookmarks.
Previously I had used the "activeTab" permission request for this, which doesn't raise any warnings. But I had some issues with that in testing so I switched to the "tabs" permission request. I did not expect this to request access to browsing history, so that comes as a surprise.
I have prepared a fixed version, 1.0.1, which should appear in the next couple of days and does not ask for the "tabs" permission.
Sorry for the scare. SuperSorter does not use browsing history at all, and should not be requesting access to it.
Regards,
Richard.