insecure-defaults

Detect fail-open insecure defaults in source code and configuration reviews.

1|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/adamatdevops/forge-works --skill insecure-defaults-adamatdevops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: insecure-defaults
Source: https://github.com/adamatdevops/forge-works/tree/main/.skills/trailofbits/insecure-defaults
Command: npx skills add https://github.com/adamatdevops/forge-works --skill insecure-defaults-adamatdevops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents insecure deployments by finding fail-open patterns where missing or misconfigured environment variables cause an app to run with weak authentication or default secrets.

Core Features & Use Cases

  • Fail-open detection: Identifies insecure defaults such as secret fallbacks and weak security flags that keep services running when configuration is absent.
  • Fail-secure distinction: Distinguishes safe crash-on-missing behavior from exploitable defaulting behavior.
  • Production-impact triage: Guides verification and evidence gathering to decide whether a finding is critical due to missing or default production configuration.
  • Use case: During a security audit of a production API, scan for environment-variable fallbacks like SECRET_KEY set via a default value, then trace runtime behavior to confirm whether production overrides it.

Quick Start

Use the insecure-defaults skill to scan the repository for fail-open environment variable fallback patterns and produce a prioritized report with file locations and verification notes.

Frequently Asked Questions about insecure-defaults

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

FAQPage Schema
What is a fail-open security misconfiguration in source code?

A fail-open security misconfiguration occurs when missing environment variables trigger weak secrets, disabled security checks, or permissive access. This Skill detects insecure defaults where missing configuration leads to vulnerable behavior instead of safe crash-on-missing failure.

How do I scan code for insecure default environment variable fallbacks?

To scan for insecure default environment variable fallbacks, use this Skill to search production-reachable paths for secret fallbacks and weak security flags. It verifies code paths and produces a prioritized report with file locations and verification notes.

Does this detect hardcoded secret fallbacks in authentication and CORS configuration?

Yes, this detects hardcoded secret fallbacks across authentication, crypto, CORS/permissions, debug features, and environment-variable handling. It distinguishes vulnerable defaulting behavior from safe fail-secure crash-on-missing patterns.

How do I distinguish fail-secure crash-on-missing behavior from exploitable defaulting?

To distinguish fail-secure behavior from exploitable defaulting, this Skill applies discovery-guided searching and code-path verification. It produces evidence-rich reporting that separates safe crash-on-missing patterns from insecure defaults.

Can I use this for a security audit of production API environment variables?

Yes, you can use this for a production API security audit. It traces runtime behavior of environment-variable fallbacks like default SECRET_KEY values to confirm whether production configuration safely overrides insecure defaults.

What is the best way to triage production impact of missing configuration defaults?

The best way to triage production impact is using this Skill's guided verification and evidence gathering. It confirms whether missing or default production configuration makes a finding critical due to fail-open behavior.