our rule is no parent relative imports outside the current folder. same folder stays ./x, anything else goes through @/ so it doesnt matter how deep the file moves later.

works fine but i know its not the only way people solve this. monorepo package boundaries, tsconfig paths, eslint rules banning the pattern outright, curious what you landed on and whether it survived contact with a big refactor

what broke first when your team tried to enforce this

I wanted a simple way to catch common issues that can easily be missed before pushing a project to production.

RepoDrift currently checks:

• Potential exposed credentials and secrets
• Dependencies and lockfiles
• Large and suspicious files
• Git status
• Basic code metrics
• Repository health

It runs locally and doesn't require uploading your source code for the current analysis.

You can install it with:

npm install -g u/repodrift/cli

Then:

repodrift scan

It's still an early project. I'm focusing on making the core analysis useful and reliable before adding AI-based explanations.

I'd like to hear from web developers: what checks would you want a tool like this to perform before deployment?

GitHub: https://github.com/GokulKir/repodrift

NPM: https://www.npmjs.com/package/@repodrift/cli