bs-detector

Analyze code snippets for hardcoded secrets and quality issues.

Updated May 11, 2026
One-click install
npx skills add https://github.com/webn77/opennexus --skill bs-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bs-detector
Source: https://github.com/webn77/opennexus/tree/main/skills/bs-detector
Command: npx skills add https://github.com/webn77/opennexus --skill bs-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers identify security vulnerabilities and code quality issues in their codebases, preventing bugs and potential leaks.

Core Features & Use Cases

  • Secret Detection: Finds hardcoded API keys, passwords, and tokens to prevent leaks.
  • Code Quality Checks: Detects empty catch blocks, usage of 'as any', console logs, and TODO comments to improve maintainability.
  • Use Case: A developer scans a JavaScript project to find and fix insecure credentials and improve code quality before deployment.

Quick Start

Use the bs-detector to analyze your code by providing the code file or block inline, and review the output for issues and suggestions.

Frequently Asked Questions about bs-detector

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

FAQPage Schema
How do I detect hardcoded secrets and API keys in my code?

To detect hardcoded secrets and API keys, you can use static analysis to scan code snippets or files. This process identifies security risks like hardcoded credentials using regex pattern matching.

Can I use static analysis to find empty catch blocks and console logs?

Yes, static analysis can find empty catch blocks and console logs. It analyzes your codebase to detect quality issues such as improper error handling and debug statements to improve maintainability.

What is the best way to scan a JavaScript project for security vulnerabilities?

The best way to scan a JavaScript project for security vulnerabilities is using static analysis. It automatically identifies quality issues and security risks like hardcoded tokens before deployment.

How do I perform a security audit on an inline code block?

To perform a security audit on an inline code block, provide the code directly to a static analysis tool. It will output identified vulnerabilities and coding standards violations for review.

Does static analysis detect TODO comments and improper error handling?

Yes, static analysis detects TODO comments and improper error handling. It reviews your code snippets to identify quality issues and suggest improvements for development processes.

What are the limitations of using regex pattern matching for code review?

Regex pattern matching for code review primarily catches predefined patterns like hardcoded secrets and debug statements. It may not identify complex logical vulnerabilities or dynamic security risks outside its static analysis scope.