Enforcing dependency as dev-dependencies

I have a crate that's meant to be used as a dev-dependencies rather than a dependencies. Now obviously if someone is so inclined they should be allowed to use it as a dependencies. But, and I promise not to so this (I'm asking purely out of curiosity), if I really wanted to, is it possible to make a crate not build if added as a plain dependencies rather than dev-dependencies?

Is there some special "I was uniquely pulled in as a `dev-dependencies" environment variable set by cargo?

I want to stress again that I promise I will not use this forbidden knowledge, should it exist.