This appears to just be an error or perhaps just a cache issue, possibly fixed in a plugin update.
If after the next full StartupPro Package update you still get the nag, let us know. But, you should be good to go on using the plugin without limitation now.