cryptographic-failures

Detect and remediate cryptographic weaknesses in software code.

20|Updated Feb 27, 2026

Search Tags:#security #encryption #cryptography #code-review #hashing #key-management #secure-randomness

Ready to run

npx skills add https://github.com/thejefflarson/soundcheck --skill cryptographic-failures-thejefflarson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cryptographic-failures
Source: https://github.com/thejefflarson/soundcheck/tree/main/.claude/skills/cryptographic-failures
Command: npx skills add https://github.com/thejefflarson/soundcheck --skill cryptographic-failures-thejefflarson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent cryptographic failures by automatically flagging insecure cryptography practices in code, such as weak hashing, insecure randomness, and hardcoded keys, reducing the risk of credential theft and data breaches.

Core Features & Use Cases

Detection: flags vulnerable cryptographic patterns in multiple languages and stacks.
Guidance: provides concrete remediation steps aligned with OWASP CWE references.
Use Case: during code review, it flags a hardcoded secret and suggests rotating to a secrets manager.

Quick Start

Run the cryptographic review pass on your codebase to identify and remediate weaknesses.

Frequently Asked Questions about cryptographic-failures

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect cryptographic weaknesses like hardcoded secrets and insecure randomness in my code?▼

You can identify cryptographic flaws by running an automated review pass that flags vulnerable patterns like weak hashing, insecure randomness, and hardcoded secrets, while providing concrete remediation steps aligned with OWASP and CWE references.

What are common cryptographic failures in software development and how can I fix them?▼

Common cryptographic failures include weak hashing, insecure randomness, and hardcoded keys. You can fix these flaws by applying concrete remediation steps during code review, such as rotating hardcoded secrets to a secrets manager to ensure post-fix compliance.

How do I check my codebase for OWASP and CWE cryptographic vulnerabilities?▼

To check your codebase for OWASP and CWE cryptographic vulnerabilities, execute a cryptographic review pass that detects insecure patterns, provides immediate fixes, and verifies post-fix compliance with established best practices and specific CWE references.

Does cryptographic flaw detection work across multiple development stacks and languages?▼

Yes, cryptographic flaw detection works across multiple languages and typical development stacks by scanning for vulnerable cryptographic patterns, guiding remediation with CWE references, and verifying compliance regardless of the specific stack used.

What is the best way to remediate hardcoded keys and weak hashing algorithms during code review?▼

The best way to remediate hardcoded keys and weak hashing during code review is to detect vulnerable patterns automatically and apply guided fixes, such as migrating hardcoded secrets to a secure secrets manager to prevent credential theft.

How do I verify post-fix compliance with cryptographic best practices after resolving weak algorithms?▼

To verify post-fix compliance with cryptographic best practices after resolving weak algorithms or insecure randomness, run a review pass that checks the remediated code against established CWE and OWASP references to ensure no flaws remain.