Repository navigation
Releases
Releases · psuvraneel-cyber/Clone-Proof
CloneProof v0.2.4
Changed
- The npm package is now
cloneproof-check: run
npx cloneproof-check check <path-or-url>or
npm install -g cloneproof-check. npm rejected the 0.2.3 publish of
clone-proofas too similar to the existingcloneproofpackage, so
0.2.3 exists only as a GitHub release. The installed command is still
cloneproof, and the GitHub release asset is now named
cloneproof-check-X.Y.Z.tgz. No scanner behavior changed.
CloneProof v0.2.3
Changed
- CloneProof is published to npm as
clone-proof: run
npx clone-proof check <path-or-url>ornpm install -g clone-proof. The
installed command is stillcloneproof, and reports and receipts still name
the toolcloneproof. The npm namecloneproofbelongs to a different
project. The Release workflow publishes the same CI-built, attested tarball
to npm with provenance; the GitHub release asset is now named
clone-proof-X.Y.Z.tgz. - Version 0.2.2 was prepared but never tagged or published; its changes
ship in this release.
Fixed
False findings measured in field test Run 6 (see
docs/FIELD_TEST.md):
- Environment checks no longer report keys that nobody configures for a
repository: variables set by the operating system or shell (HOMEPATH,
PROGRAMFILES,OLDPWD,COMP_CWORD,XDG_*), by Git while it runs hooks
(GIT_DIR,GIT_INDEX_FILE), by CI services (TRAVIS,TF_BUILD,
CF_PAGES, …), by Rollup (ROLLUP_WATCH, when Rollup is a dependency), and
keys the repository's own code assigns, such asprocess.env.WEBPACK_SERVE = 'true'. - Environment keys mentioned only in comments or in
.d.tstype declarations
are no longer counted, and keys containing$are read whole
(process.env.Wimp$ScrapDirwas reported asWimp). NO_TESTS_FOUNDnow recognizes shell test suites (test.sh,test/*.sh,
Bats) and other languages' test files (Dart and Go*_test, Python
test_*, Ruby*_spec). A repository with such tests and no test script
fails withTEST_SCRIPT_MISSING, as it does for JavaScript tests.ENGINES_NODE_UNSATISFIEDno longer misreadsengines.noderanges with a
space after the operator, such as>= 24.10.0.PRIVATE_REGISTRYno longer reports public npm mirrors (npmmirror, Tencent
Cloud, Huawei Cloud).
CloneProof v0.2.1
Fixed
README_SCRIPT_UNKNOWNno longer fails library READMEs that show readers
how to use the package in their own project. A script defined in a fenced
"scripts": { ... }example in the README, and missing from the root
package.json, is reported under the informational
README_OTHER_PROJECT_COMMANDSinstead.npm runcommands that appear as
quoted values in README configuration examples (for example
"cover": "npm run cover:unit") are no longer treated as commands. In field
test Run 6, all 9README_SCRIPT_UNKNOWNfindings were of these kinds, and
the repositories failingcheckfell from 6 to 1 (see
docs/FIELD_TEST.md).
CloneProof v0.2.0
Changed
- Exit behavior: a repository with no tests no longer fails
check. When
there is no test script (or only npm's placeholder) and no test files or
README test instructions, CloneProof reports the newNO_TESTS_FOUND
warning instead of failing withTEST_SCRIPT_MISSING/
TEST_SCRIPT_PLACEHOLDER. A missing or placeholder test script still fails
when the repository has tests thatnpm testcannot run, and whenever the
scan is incomplete.verifystill requires a test script. - For this decision, test files are
*.test.*,*.spec.*, Cypress*.cy.*,
files in__tests__/, and files undertest/ortests/that use a test
API. Other files undertest/(dev playgrounds, examples) do not count.
Added
--require-testsforcheckandverify, and the Action input
require-tests, to treat a repository without tests as failed.
CloneProof v0.1.1
Changed
- The GitHub Action is named
CloneProof Checkso it can be listed on the
GitHub Marketplace, where the nameCloneproofbelongs to a different
project. Theuses: psuvraneel-cyber/Clone-Proof@<ref>reference, inputs,
and outputs are unchanged.
Fixed
ENV_EXAMPLE_MISSING/ENV_KEY_MISSING: committed root.envfiles
(for example.env.developmentor.env.default) now count as
documentation. Only key names are read; values are never stored or
reported. Gitignored local.envfiles still do not count.- Environment checks no longer report keys that a framework or build tool
sets itself: Vite'simport.meta.envMODE,BASE_URL,PROD,DEV,
andSSR; WXT, Astro, create-react-app, and Next.js keys when that
framework is a dependency; and keys injected through a build-time define
map such as webpackDefinePlugin. BROWSER_TESTS_DETECTEDno longer fires just because Playwright or a
Vitest browser package is installed. Vitest now counts only when the test
command passes--browseror a configuration it loads sets
browser.enabled: true. Dedicated browser runners are reported as before.
CloneProof v0.1.0
First tagged release.
Added
cloneproof check <path-or-github-url>: read-only static inspection of a
Node.js/TypeScript repository root. It never runs repository code. Public
GitHub URLs get a size and visibility preflight, then one isolated shallow
clone with an empty Git configuration.cloneproof verify --docker --execute: opt-innpm ci --ignore-scriptsand
npm testinside the pinned image
node:22.19.0-bookworm-slim@sha256:4a4884e8a44826194dff92ba316264f392056cbe243dcc9fd3551e71cea02b90,
with no network by default, a non-root user, dropped capabilities, a
read-only source mount, resource limits, and guaranteed cleanup.cloneproof setupto prepare the pinned verifier image explicitly.- Deterministic text, JSON (schema version 2), and self-contained HTML reports
with relative paths, explicitcoverage.checked/coverage.notChecked
lists, and bounded evidence. - 86 documented finding codes, including
VERIFY_NO_TESTS_RAN, which fails a
verification whose test command exits0without running any tests. - A native GitHub Action (
node24) withcheckandverifymodes,
workflow annotations, and a Job Summary. Docker verification from the Action
runs only on Linux runners forpushandworkflow_dispatchevents. - Versioned reproducibility receipts (
receiptVersion: 1):--receipt FILE
oncheckandverify,cloneproof receipt verify <file>, and Action
receipt-path/receipt-statusoutputs. The SHA-256 digest detects
accidental changes; it is not a signature. See docs/RECEIPTS.md. - Release tarballs built by CI from version tags, published with
SHA256SUMSand a build-provenance attestation; see
docs/RELEASING.md.
Security
- Repository targets are treated as untrusted input; see
docs/SECURITY.md for the trust boundary and its limits.
Docker is not a complete sandbox, and--allow-networkshould be used only
for trusted repositories.