'scanner' 검색 결과

Plan, review, and retire feature flags, switches that control feature availability. Includes tools to identify aging flags, generate phased release schedules, and check that documentation records ownership and emergency shutdown procedures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan a phased release for a new feature
• Identify old flags for cleanup
• Audit emergency shutdown documentation

Compare documented permissions and data boundaries with actual code to find meaningful gaps. Produce findings that connect each documented rule to implementation evidence, identify who could exploit it and who is affected, and propose a concrete fix.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing code built by AI agents
• Checking access controls against documented permissions
• Finding gaps between documentation and code

Review agent skills for risky behavior, excessive permissions, and hidden data sharing. It combines static scanning, which checks known risk patterns without running code, with source review to produce an evidence-based installation verdict.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a skill before installation
• Checking permissions in an installed skill
• Investigating credential access or external data sharing

Assess a brand’s presence on YouTube, Reddit, Wikipedia, LinkedIn, and other sources relevant to AI search. Review mentions, official profiles, and discussion sentiment, then produce a weighted authority score and recommendations for each platform.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing brand mentions across major platforms
• Assessing positive and negative Reddit discussions
• Checking Wikipedia and Wikidata presence

Review code or changes for exposed secrets, injection risks, weak encryption, and missing permission checks. Produce a structured report with severity, location, recommendations, and confidence, with a separate reviewer checking findings for false positives.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a module for security issues
• Checking changes for exposed secrets
• Preparing a vulnerability report with evidence

Run an AI vulnerability scan on uncommitted changes, changes against main, or an entire codebase. Filter candidate files, investigate potential security issues, and review findings with severity ratings, with options to revalidate and export results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking uncommitted changes for vulnerabilities
• Reviewing security issues in changes against main
• Scanning an existing codebase

Review TON smart contracts written in FunC for three security patterns: incorrect boolean values, unverified Jetton token notifications, and forwarding funds without reserving execution fees. Receive a coverage table, source references, severity ratings, and suggested fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review FunC boolean logic
• Check sender validation in Jetton transfer notifications
• Inspect forwarded TON amounts and execution fee reserves

Review Substrate and Polkadot runtime modules, called pallets, for seven security patterns, including unsafe arithmetic, crashes, incorrect processing costs, and weak permission checks. Produce a complete coverage table, findings with code references, and proposed fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing custom Substrate pallets
• Reviewing processing costs and fees
• Checking permissions for privileged operations

Review Cairo smart contracts on StarkNet for six vulnerability patterns involving arithmetic, cross-layer messages, addresses, and signature reuse. Receive a coverage table with evidence for every pattern, plus severity ratings and fixes for identified issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review StarkNet contracts before launch
• Audit L1-L2 bridge message handling
• Check protection against signature reuse

Review Cosmos SDK modules and CosmWasm contracts for vulnerabilities that could halt a chain, cause fund loss, or produce inconsistent state. Findings are checked against consensus execution paths and saved as individual Markdown reports with severity and fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing custom Cosmos SDK modules
• Reviewing IBC integrations
• Assessing chain security before launch

Review Solana and Anchor programs for six security patterns, including unsafe calls to other programs and missing account checks. Receive a complete coverage table, findings with file references and severity, and suggested fixes for identified issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing Solana programs before launch
• Checking calls to other programs and their program IDs
• Inspecting address derivation and account validation

Reviews Algorand smart contracts written in TEAL or PyTeal for 11 vulnerability patterns. Produces a complete coverage table and findings with code references, severity ratings, and suggested fixes, with optional automated checks using Tealer.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Security checks before an Algorand contract audit
• Reviewing TEAL or PyTeal transaction validation
• Verifying fixes for reported vulnerabilities

Scan Android APK files for Firebase configuration and access-control weaknesses in databases, storage, authentication, and cloud functions. Produce text and JSON reports with evidence, severity ratings, and suggested fixes for authorized security assessments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing Firebase security in Android apps
• Checking unauthenticated database access
• Testing storage listing and write permissions

Assess AWS, Azure, and GCP environments by identifying identities, permissions, and paths to broader access or data exposure. Covers cloud storage, secrets, cross-account trust, and CI/CD, the automated systems used to build and deploy software.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning an AWS, Azure, or GCP security assessment
• Tracing privilege escalation from current permissions
• Reviewing CI/CD credentials and OIDC trust settings

Review agent skills before installation or during use by inspecting their files without running code. Local checks identify risks such as credential theft, permission abuse, and differences between stated purpose and actual behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a skill before installation
• Auditing all installed skills on an agent platform
• Checking whether code matches the stated purpose

Scan code for security risks such as injection attacks and embedded secrets, then report findings by severity. Also check whether design documents record security decisions, trust boundaries, and accepted risks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Security checks before committing code
• Reviewing authentication and authorization changes
• Finding embedded keys and secrets

Check a software module’s folder structure, required README.md and DESIGN.md files, and whether documentation matches the code. Produce a report identifying missing content and issues to resolve before handoff.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking a newly created module before handoff
• Reviewing documentation after refactoring
• Finding missing README.md and DESIGN.md sections

Introduce nullable reference types into an existing C# project, making explicit which references may be null. Plan a staged migration, resolve compiler warnings, and clarify public API annotations while preserving runtime behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adopting nullable reference types in an existing C# project
• Migrating a large codebase file by file
• Clarifying nullability in public APIs

Review CI/CD pipelines, the workflows that build and release software, for unsafe code execution, exposed secrets, and excessive permissions. Combine automated scanning with manual checks to document reproducible findings and suggested fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing GitHub Actions workflows
• Checking secrets and token permissions
• Inspecting self-hosted runners

Review terms of service and privacy policies from a consumer's perspective. Identify risks involving subscriptions, data use, liability, and content rights, then produce a structured report with supporting passages, severity assessments, and practical actions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking subscription renewal and cancellation terms
• Reviewing data collection and sharing permissions
• Examining platform rights over posted content

Security best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus `gosec` SAST, race detection, and fuzz testing. Apply when writing, reviewing, or auditing Go code for security, or when touching crypto, file or network I/O, secrets, user input, or authentication. Not for non-exploitable defensive bugs such as nil panics or slice aliasing (→ See `samber/cc-skills-golang@golang-safety` skill), dependency vulnerability scanning with govulncheck (→ See `samber/cc-skills-golang@golang-dependency-management` skill), or wiring security scanners into CI pipelines (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go project CI, writing or fixing `.github/workflows/*.yml`, adding a linter or security scanner as a pipeline job, wiring automated dependency-update bots, or adding quality gates. Covers wiring tools into a pipeline, not the analysis they perform: do NOT use for choosing or interpreting security findings (→ See `samber/cc-skills-golang@golang-security` skill) or for choosing, upgrading, or auditing dependency versions (→ See `samber/cc-skills-golang@golang-dependency-management` skill).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure AWS Security Agent for the current workspace — provision or reuse an agent space, IAM service role, and S3 bucket. Use when the user asks to "set up security agent", "configure security scanner", "is security agent configured", or on first-time use before any scan or pentest.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds, runs, debugs, and operates applications on AWS Lambda MicroVMs — Firecracker-isolated, snapshot-resumable serverless compute environments running inside a container with up to 8 hr lifetimes. Applicable when workloads need strong isolation between tenants, isolated serverless compute, sandbox compute, or secure multi-tenant execution. Also suited for AI/agent code-execution sandboxes, interactive code playgrounds and notebooks (Jupyter, REPLs, dev environments running user-supplied code), reinforcement-learning environments, multi-tenant CI executors and build runners, sessionful game or simulation servers, or isolated security scanners. Also applicable when the workload needs long-lived sessions, a real port-listening server (gRPC, WebSocket, custom TCP protocols), state preserved across periods of inactivity (suspend/resume), container-level access (FUSE, eBPF, custom syscalls), or session-affine routing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.