Forensic code auditing

Cryptographic proof for every line of code

Record every keystroke. Sign every session. Chain every hash. Tamper-proof .integrity files that stand up in any audit.

terminal
$origin verify session_2024-01-15.integrity
verifying #247...

How it works

01

Record

Every keystroke, edit, save, and cursor movement is captured as a structured event with precise timestamps.

02

Sign & Seal

Each session is signed with Ed25519 keys. Events are chained with SHA-256 into an immutable sequence.

03

Verify

Upload any .integrity file to independently verify the complete chain — every hash and signature.

Capabilities

Hash Chain Integrity

Each event hash depends on its predecessor. Break one link, invalidate the entire chain.

Cryptographic Signatures

Ed25519 signatures bind sessions to authors. Non-repudiable proof of authorship.

Self-Contained Proof

ZIP archives with manifest, signatures, events, and source. Everything for independent audit.

Keystroke Granularity

Every keystroke, cursor move, and edit individually recorded with precise timestamps.

Visual Replay

Step through edits in real-time. Watch code being written keystroke by keystroke.

Authorship Analysis

Typing speed, pause patterns, and behavioral metrics for forensic profiling.

Built for universities

Academic integrity shouldn't rely on heuristics alone. Origin gives institutions cryptographic certainty about who wrote the code.

CS Departments

Verify that submitted code was actually written by the student — keystroke by keystroke. Cryptographic proof, not plagiarism heuristics.

Academic Integrity

Tamper-proof, timestamped evidence chains for review boards. Not screenshots of MOSS reports.

Research Labs

Settle authorship disputes on published code with cryptographic attribution, not commit history.

See it in action

Upload an .integrity file and watch verification happen in real-time.

Open Dashboard