insecure-defaults

Detect fail-open security vulnerabilities and insecure default configurations in source code and deployment manifests.

Updated Nov 23, 2025
One-click install
npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill insecure-defaults-manuelbrandner85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: insecure-defaults
Source: https://github.com/manuelbrandner85/Weltenbibliothekapp/tree/main/.agents/skills/insecure-defaults
Command: npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill insecure-defaults-manuelbrandner85

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill detects fail-open security vulnerabilities where applications run with insecure default configurations, such as hardcoded secrets, weak authentication, or permissive access controls.

Core Features & Use Cases

  • Secret Detection: Identifies hardcoded credentials and fallback secrets that expose production environments.
  • Configuration Auditing: Scans for weak defaults like permissive CORS, disabled authentication, or insecure cryptographic algorithms.
  • Use Case: During a security review, use this Skill to scan your codebase for environment variable fallbacks that might allow an application to start with insecure default keys in a production container.

Quick Start

Use the insecure-defaults skill to audit the current repository for hardcoded secrets and fail-open configuration patterns.

Frequently Asked Questions about insecure-defaults

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

FAQPage Schema
How do I scan my codebase for hardcoded secrets and insecure default configurations?

To scan for insecure default configurations, use a security audit skill to analyze environment variable handling and authentication logic, detecting hardcoded credentials and fail-open vulnerabilities in source code.

What are fail-open security vulnerabilities and how do they affect production environments?

Fail-open security vulnerabilities occur when applications start with insecure defaults, such as fallback secrets or disabled authentication, allowing production containers to run without proper cryptographic protections or access controls.

Can I audit deployment manifests for weak cryptographic implementations and permissive CORS?

Yes, you can audit deployment manifests by analyzing environment variable fallbacks and configuration patterns to identify weak cryptographic algorithms, permissive CORS, and disabled authentication logic.

How do I detect environment variable fallbacks that allow insecure default keys in production?

Detect environment variable fallbacks by using pattern matching to validate code paths and configuration fallbacks, identifying where applications might start with insecure default keys in a production container.

Does this security audit require specific tools to analyze authentication logic and configuration patterns?

The security audit requires grep and bash-based pattern matching tools to validate code paths and configuration fallbacks, analyzing authentication logic and cryptographic implementations within the source code.

What is the best way to automate DevSecOps compliance checks for production-reachable security risks?

Automate DevSecOps compliance by scanning application source code and deployment manifests to identify production-reachable risks, detecting hardcoded secrets and fail-open configuration patterns during security reviews.