ck:security-scan

Detect secrets, vulnerable dependencies, and insecure code patterns in codebases.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/hotriluan/alkana_web --skill ck-security-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:security-scan
Source: https://github.com/hotriluan/alkana_web/tree/main/.opencode/skills/security-scan
Command: npx skills add https://github.com/hotriluan/alkana_web --skill ck-security-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the detection of secrets, vulnerable dependencies, and insecure code patterns in a codebase to prevent leaks and insecure deployments.

Core Features & Use Cases

  • Secrets detection using regex patterns to locate API keys, tokens, and credentials in code and configuration files.
  • Dependency audit across Node.js, Python, Go, and other ecosystems to identify known vulnerabilities.
  • Code pattern analysis aligned with OWASP-top patterns to surface risky constructs.
  • Use Case: Before releases or during code reviews, run a security scan to generate a risk report.

Quick Start

Run the security scan on the current project to detect secrets, dependency issues, and code patterns.

Frequently Asked Questions about ck:security-scan

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

FAQPage Schema
How do I detect secrets and API keys in my codebase before release?

A security scan detects secrets by applying regex patterns to code and configuration files, identifying exposed API keys, tokens, and credentials to prevent leaks and insecure deployments before release.

Can I scan vulnerable dependencies across Node.js, Python, and Go projects?

Yes, dependency audits identify known vulnerabilities across Node.js, Python, and Go ecosystems by analyzing lockfiles and manifests, producing a report of vulnerable packages during pre-release security checks.

What is OWASP code pattern analysis and how does it find insecure code?

OWASP code pattern analysis identifies insecure code constructs by scanning the codebase against predefined references aligned with OWASP-top patterns, surfacing risky logic during code reviews and ongoing security audits.

Does this security scan work for ongoing audits or just pre-release code reviews?

The security scan supports both pre-release code reviews and ongoing audits by continuously detecting secrets, vulnerable dependencies, and insecure code patterns across multiple ecosystems to maintain long-term codebase security.

What's the best way to automate vulnerability detection for multiple ecosystems?

Automate vulnerability detection by running a unified security scan that executes dependency audits and regex-based code analysis across Node.js, Python, and Go, consolidating secrets and insecure patterns into a comprehensive risk report.

Why does dependency audit report known vulnerabilities during my security scan?

Dependency audits report known vulnerabilities by cross-referencing project manifests against vulnerability databases, identifying compromised or outdated packages in Node.js, Python, and Go ecosystems to prevent insecure deployments.