@sebastienrousseau/crypto-lspLanguage Server Protocol (LSP) providing real-time cryptographic static analysis, quantum-vulnerability flagging, PEM/OpenPGP validation, and automated quick fixes for IDEs (VS Code, NeoVim, JetBrains, Emacs).
@sebastienrousseau/crypto-lsp brings institutional-grade cryptographic intelligence directly into developer IDEs via the Language Server Protocol (LSP 3.17). It actively monitors code buffers for broken primitives, inadequate key sizes, quantum vulnerabilities (Harvest-Now-Decrypt-Later risks), hardcoded secret material, and malformed PEM/OpenPGP blocks.
CRYPTO-001: Detects broken hash functions (MD5, SHA-1, MD4, RIPEMD160).CRYPTO-002: Detects insecure symmetric ciphers and modes (DES, 3DES, RC4, ECB mode).CRYPTO-003: Flags inadequate RSA key sizes (< 2048 bits).CRYPTO-004: Quantum Vulnerability Flagging for classical public-key cryptography (RSA, ECDSA, ECDH, Ed25519) in long-term data security contexts.CRYPTO-005: Flags hardcoded secret/private keys in source files.CRYPTO-006: Validates PEM and OpenPGP armored block syntax.MD5 -> SHA-256).aes-128-ecb -> aes-256-gcm).# Global installation
pnpm add -g @sebastienrousseau/crypto-lsp
# Run stdio LSP server
crypto-lsp --stdio
Configure in your .vscode/settings.json:
{
"crypto.lsp.serverPath": "crypto-lsp"
}
vim.lsp.start({
name = 'crypto-lsp',
cmd = {'crypto-lsp', '--stdio'},
root_dir = vim.fs.dirname(vim.fs.find({'package.json', '.git'}, { upward = true })[1]),
})
pnpm --filter @sebastienrousseau/crypto-lsp run build
pnpm --filter @sebastienrousseau/crypto-lsp run test
pnpm --filter @sebastienrousseau/crypto-lsp run lint
pnpm --filter @sebastienrousseau/crypto-lsp run format
All 18 packages in the Crypto Service workspace maintain a 100% coverage floor across statements, branches, functions, and lines.
Versions advance strictly one step at a time on the 0.0.x line (v0.0.1 → v0.0.2 → v0.0.3 ... → v0.0.999 → v0.1.0). Work for every release iteration begins on a dedicated feat/v<version> branch.
All 18 packages in the workspace move in lockstep. Public API signatures, cipher output formats, and serialization schemas are strictly versioned. Breaking changes to serialized formats or algorithm defaults are considered major breaking changes. Minimum toolchain upgrades (e.g. Node.js LTS floor) are governed by POLICIES.md.
Dual-licensed under Apache 2.0 or MIT, at your option.
Copyright (c) 2022-2026 Sebastien Rousseau and The Crypto Service Suite contributors.