Requirements
Installation
kennet --version prints the version.
Usage
Name each repository as a path to a clone or as a git URL. With none, it uses the current directory.- Prints what it sends and a sign-in link with a code, and opens the link in your browser. Approve the code there. This is your only step. Nothing is built or sent before you approve, and a denied or expired code sends nothing.
- Reads each repository’s history and sends the profile.
- Builds and tests the latest commit, then the past commits Metaphi AI names. It also swaps single operators at the latest commit, such as
<for<=, and runs the tests over each swap. Each progress line shows about how long is left. - Sends the results and prints a reference,
cv_.... Keep it: it identifies your submission.
kennet org create "Acme".
Data security
Builds and tests run in temporary copies on your machine. CodeVal sends typed measurements of your repositories: every value is a number, a yes or no, a choice from a fixed list, an id or a key. No field takes free text. Metaphi AI checks the tip and root commit ids and the git blob ids it receives against Software Heritage’s public archive, to see whether the code is already public.Data collected
Counts and ids for files, commits and authors; the shape of commit history; build and test results as typed outcomes. No source code, logs, file paths, author names or commit text. Public dependency names and standard build-file names are included. Files, folders, authors and commits are numbered within the submission. A key is a 16-character HMAC under a key kept on your machine: equal inputs give equal keys within one repository, and the input cannot be read back from it. Repository, sent once
Commits, for each
Files, for each
Results, for each batch of up to 5 commits and 5 operator swaps
Steps, for each build and test run in the results
Metaphi AI’s server refuses any field not listed here.
What Metaphi AI asks for, in each batch
Safeguards
Options
It finds how a repository builds and tests from its CI configuration, container files and build files. If your repository builds and tests with a command of its own, give it after
--, and run that repository on its own:
KENNET_TESTS, KENNET_JUNIT (a directory for JUnit XML) and KENNET_JOBS (how many jobs to run at once).
Errors
If a run stops, run the same command again. It goes on from the last finished unit and runs nothing twice.
With
--json, a failure prints {"error": {"code", "message", "next_step"}}. next_step is the command that clears it, or null.