skills.rest
florianbuetow
florianbuetowCOMMUNITY
Explore all skills by this author →
Website𝕏@bytetweetsGitHub

detecting

Analyze source code for detectability threats and generate constant-time fixes.

12|1|Updated Feb 9, 2026
Search Tags:#code analysis#security#privacy#side channels#detectability#linddun
One-click install
npx skills add https://github.com/florianbuetow/claude-code --skill detecting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: detecting
Source: https://github.com/florianbuetow/claude-code/tree/main/plugins/appsec/skills/detecting
Command: npx skills add https://github.com/florianbuetow/claude-code --skill detecting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies privacy vulnerabilities in your code related to detectability, helping you prevent sensitive information from being inadvertently exposed through system interactions or metadata.

Core Features & Use Cases

  • Detectability Analysis: Analyzes code for threats where an observer can infer user interaction or data existence without direct content access.
  • Privacy Leakage Identification: Pinpoints issues like timing side channels, metadata leakage, and enumeration surfaces.
  • Use Case: Ensure your application doesn't leak user information through subtle timing differences in API responses or by revealing the existence of records via error messages.

Quick Start

Analyze the current code changes for detectability issues.

Frequently Asked Questions about detecting

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

FAQPage Schema
How do I detect timing side channels in my source code?▼

Detecting timing side channels involves analyzing source code to find privacy vulnerabilities where observers infer sensitive data from response time differences, mapping results directly to the LINDDUN D1 detectability category.

What is a detectability threat in privacy engineering?▼

A detectability threat occurs when an observer infers user interaction or data existence without direct content access, often through metadata leakage or timing side channels, violating LINDDUN undetectability and unobservability properties.

How do I fix metadata leakage and enumeration surfaces in my application?▼

Fixing metadata leakage and enumeration surfaces involves analyzing code for detectability issues and using a `--fix` flag to generate constant-time responses and uniform error handling, preventing record existence inference.

Does LINDDUN privacy analysis support different code analysis depths?▼

LINDDUN privacy analysis supports various analysis depths for detecting privacy property violations, allowing you to adjust the scrutiny level applied when scanning source code for detectability threats and metadata leakage.

Why does my API reveal if a user record exists through error messages?▼

APIs reveal record existence through non-uniform error messages, a detectability threat where observers infer data existence without direct content access, which you can resolve by enforcing uniform error handling.

Related Skills

Explore More Software Engineering Skills→
florianbuetowflorianbuetow
12

linddun

Performs LINDDUN privacy threat analysis across seven categories using specialized subagents in parallel.

Community
Advanced
safzanpiranisafzanpirani
1

deslop

Remove redundant and suboptimal code sections from AI-generated source files.

Community
Basic
florianbuetowflorianbuetow
12

non-repudiation-privacy

Analyze source code for non-repudiation privacy threats from audit logging and digital signatures.

Community
Advanced
ToanPV90ToanPV90

sast-scanning

Detects source code vulnerabilities via static analysis with JSON/SARIF outputs.

Community
Advanced