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.

来源