Nothing to worry about.
Its just a message that notify you that given
site shows that message, so you can accept it,
or deny it, or ignore, just like you would do
in regular browser. And if you want to allow or deny
it you just have to define it before that message is shown,
just like the blue message in BAS says.
I think this result reflect the average of real browsers appropriate as many (Chrome) users are surfing with the standard (pre-installed) plugins and therefore the fingerprints for the plugins are the same as it should.
It's possible to use FingerprintDetector inside FingerprintMaganer without BAS?
I didn't find any way.
If not, can you implement it?
Why is this necessary? FingerprintMaganer is designed to manually manage profiles, and FingerprintDetector is designed to detect possible parameters by which the site can identify you (all these parameters are emulated by FingerprintSwitcher)