Can your Node.js repository survive a fresh clone? I'm looking for developers to test my open-source tool

Описание и применение

Clone‑Proof проверяет готовность репозитория Node.js к клонированию, выявляя проблемы с зависимостями, тестами и переменными окружения, а также может выполнять проверку в изолированном Docker‑контейнере.

Задача

Open‑source Node.js projects often fail to run correctly after a fresh clone due to missing lockfiles, nonexistent test commands, undocumented environment variables, conflicting Node.js version declarations, or mismatched dependencies and setup instructions.

Результат

Clone‑Proof provides static inspection of manifests, lockfiles, test scripts, Node.js declarations, env vars, and more, and optionally verifies installation and test execution in a sandboxed Docker container, producing actionable findings with file‑and‑line evidence.

Рабочий процесс

• Run static check: npx cloneproof-check check . or npx cloneproof-check check https://github.com/OWNER/REPO
• Optionally run Docker verification: npx cloneproof-check verify . --docker --execute (add --allow-network if needed)
• Integrate into GitHub Actions with a workflow step using psuvraneel-cyber/[email protected]

Доказательства

Clone-Proof is a repository readiness checker for Node.js and TypeScript projects.

Источник

It examines things such as: Package manifests and lockfiles, Package-manager consistency, Test scripts and README commands, Node.js runtime declarations, Environment-variable documentation, Gitignored core files, Browser-test and service dependency indicators.

Источник

It attempts to install dependencies using npm ci --ignore-scripts and execute the declared test workflow inside a pinned, restricted container.

Источник

You can integrate it into your existing CI workflow to receive: Workflow annotations, GitHub Actions Job Summaries, Static check results, Optional Docker verification, Reproducibility receipts.

Источник

I've conducted field testing against public Node.js and npm repositories, including a 100-repository evaluation.

Источник