Ideas · Builder Notes
@kognita/verify: checking Kognita evidence without Kognita
The independent TypeScript verifier from Kognita alpha 0.7.0 is now published on npm as @kognita/verify, so a reviewer can check an evidence chain without running the Python package.
What was the problem?
A verifier written by the same people, in the same language, as the system it checks is not very independent. An examiner should be able to check the chain with different code.
What did I build?
@kognita/verify and its kognita-verify CLI are a separate TypeScript implementation with zero runtime dependencies, using built-in Ed25519 and SHA-256. Shared fixtures make the Python and TypeScript verifiers agree, and CI runs it on Node 22. Version 0.7.0 is on npm.
Why JavaScript?
It runs almost anywhere a reviewer already works, and a second language makes a shared bug less likely.
What's still open?
Publishing is manual for now. There is no npm publication workflow in the repository yet.
What would I tell another builder?
If you claim evidence is tamper-evident, give people a way to check it that does not depend on you.
Sources
Kognita is an open-source alpha. This note comes from @kognita/verify on npm, Kognita CHANGELOG: 0.7.0, Kognita verify-ts in the Kognita repository.