quipnetwork/hashsigs-ts

★ 11,544TypeScriptAudience · developerComplexity · 3/5LicenseSetup · easy

Mindmap

mindmap
  root((repo))
    What It Does
      WOTS+ signatures
      Post-quantum crypto
      TypeScript library
    Tech Stack
      TypeScript
      Vitest
      npm
    Use Cases
      Quantum-safe signing
      Web3 integration
      Browser crypto
    Testing
      80 percent coverage
      HTML and JSON reports
    Audience
      Web developers
      Crypto builders

mindmap root((repo)) What It Does WOTS+ signatures Post-quantum crypto TypeScript library Tech Stack TypeScript Vitest npm Use Cases Quantum-safe signing Web3 integration Browser crypto Testing 80 percent coverage HTML and JSON reports Audience Web developers Crypto builders

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Add quantum-resistant digital signatures to a TypeScript or JavaScript project by installing from npm

USE CASE 2

Verify post-quantum WOTS+ signatures inside a browser app or Node.js backend without any native dependencies

USE CASE 3

Integrate hash-based signing into a web3 project that needs long-term cryptographic security against quantum attacks

Tech stack

TypeScriptVitestnpm

Getting it running

Difficulty · easy Time to first run · 30min

AGPL-3.0 license requires sharing source if used in a network service, no usage examples are included in the README.

Source code must remain open under AGPL-3.0, if you use this in a network service, you must publish your modified source code to anyone who asks.

In plain English

Hashsigs-ts is a TypeScript library that implements a type of cryptographic signing called WOTS+, which stands for Winternitz One-Time Signature Plus. Digital signatures are a way to prove that a piece of data was produced by a specific party and has not been changed. Most signing systems today rely on the mathematics of elliptic curves or large number factoring, but hash-based signatures like WOTS+ rely only on hash functions, which are considered resistant to attacks from quantum computers. The library is published to the npm registry, so it can be added to any TypeScript or JavaScript project with a single install command. It is built from source using standard TypeScript tooling, and the repository includes a watch mode for active development. The project uses Vitest for testing and enforces minimum coverage thresholds of 80% across functions, branches, and statements. Coverage reports can be generated in HTML, JSON, and LCOV formats. The LCOV output is intended for integration with continuous integration systems. The README is brief and does not include usage examples or API documentation beyond installation and build commands. The library appears to be an early or specialized release, and the star count likely reflects interest in post-quantum cryptography tooling rather than broad adoption. It is released under the GNU Affero General Public License version 3, which requires that source code be shared when the software is used to provide a network service.

Copy-paste prompts

Prompt 1

I installed hashsigs-ts from npm. Show me how to generate a WOTS+ key pair, sign a message, and verify the signature in TypeScript, and explain why I must never reuse the same key pair.

Prompt 2

Help me integrate hashsigs-ts into my Next.js API route so that each user action is signed with a one-time WOTS+ key before being recorded.

Prompt 3

I want to use hashsigs-ts in a project licensed under MIT. Is there a conflict with the AGPL-3.0 license, and what do I need to do to comply?

Prompt 4

Set up the hashsigs-ts repo locally, run the Vitest test suite, and generate an HTML coverage report. Walk me through each step.

Open on GitHub → Explain another repo

← quipnetwork on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.