First of all, every behavior of a library one is releasing to the public should be documented; failing that simple requirement, I would say your dependency was unfit for public distribution.
Also, environment variables are pretty common in most projects, so one has to be careful to avoid naming conflicts. It should be best practice to have a namespace for your environment variables, e.g. if your project is called foo, prefix them with FOO_NAME instead of just going with NAME.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
First of all, every behavior of a library one is releasing to the public should be documented; failing that simple requirement, I would say your dependency was unfit for public distribution.
Also, environment variables are pretty common in most projects, so one has to be careful to avoid naming conflicts. It should be best practice to have a namespace for your environment variables, e.g. if your project is called foo, prefix them with
FOO_NAMEinstead of just going withNAME.