Why I built a new ENV analyzer in rust?

In projects I saw a same problem most of the time and it caused by my AI Some Environment variables will defined in code but not configured in .env file or not included in env.sample for documentation purpose It happens because my AI agent forgot this env variable from context

When i run my package it will analyze the whole codebase and find where env config is mismatched and where I added variable in codebase and forgot to add it in .env file or included in .env file but forgot to add or mismatch name in codebase

So I built a Rust engine which will work on my JS,TS codebase but why rust? Its simple Rust is fast compare to JS engine I made my rust engine work both rust and TS/JS codebase Then I research about this engine and find out many developers face this same problem day to day life

So, I published my engine in both crate.io and npmjs registry I added more language support python,Go,Bash and much more in crate i got 33 install and npmjs is 626 installation so far Its been 3 days since I published my package in both registry

I tested it in windows, Linux and macOS and it is open source For NPM package I just build the rust code in native machine code and added npm wrapper around it

GitHub Link - https://github.com/jayasurya261/envdoc
NPM Registry - https://www.npmjs.com/package/envdoc-cli
Crate.io - https://crates.io/crates/envdoc

For future updated I thought about creating a .env file with autocompleted variable defined by analyzed codebase
Which features can I add in this package for future updated?