Clone-Safe UPM Guard

🧪 Make Every Clone Ready

A project may work on your computer but fail when a teammate or CI downloads it.

A missing local package, private file path, Git LFS pointer, or unsafe Git reference can stop the project from opening correctly. Clone-Safe UPM Guard finds these risks before they become someone else’s problem.

🔍 Find the Exact Package Problem

The tool checks manifest.json, packages-lock.json, embedded packages, local packages, Git dependencies, Git LFS content, scoped registries, and package compatibility.

Each result shows the package, file, JSON path, safe evidence, severity, possible result, and a suggested manual fix. This helps you understand both the problem and what to check next.

📦 Check Common Package Sources

Clone-Safe UPM Guard understands registry packages, built-in packages, local folders, local tarballs, Git packages, and embedded packages.

It can find missing paths, paths that escape the project, wrong file types, unsafe separators, case problems, mutable Git references, embedded package shadowing, and registry routing issues.

🚦 Get Honest Results

Confirmed local blockers stay separate from warnings and remote checks that cannot be proven offline.

The tool does not claim that a remote package is available when it cannot check the server. This gives your team clear results without creating false confidence.

⚙️ Use It Locally or in CI

Create repeatable JSON reports for code review and automated builds. Reviewed baselines help your team track approved results without hiding new problems.

Stable batch exit codes make it easy to stop CI when a confirmed package blocker is found.

🛡️ Offline and Read-Only

Clone-Safe UPM Guard does not contact package servers or Git hosts. It does not install, remove, resolve, embed, or upgrade packages.

It also does not edit package files, change Git data, or apply automatic fixes. Your project stays under your control.