安全软件
点击放大

A comprehensi scanner you can run against any codebase from Claude Code. Finds hardcoded secrets, injection flaws, auth issues, misconfigurations, AI-specific , and more.
Covers OWASP Top 10 (2025), OWASP Mobile Top 10 (2024), and OWASP LLM Top 10 (2025).
---
This section exists because we belie starts before you write a single line of code. It starts with the tools you choose to trust.
Claude Code plugins, MCP servers, custom skills, GPT Actions, IDE extensions — the entire ecosystem of AI de tooling shares a fundamental problem: most of it runs with your pri, on your machine, with access to your code.
When you install a plugin, you are giving it:
This is not a theoretical risk. A malicious or compromised plugin could exfiltrate your source code, steal credentials from your en, inject backdoors into your codebase, or silently alter your AI assistant's behavior.
1. Read the source code.
Every plugin you install should be open source. If it isn't, don't install it. Before installing, actually read:
curl to exfiltrate your code every time you start a session. Look at every command field in any hooks config.scripts/ or bin/ directories. Don't run binaries you can't inspect.settings.json that changes your Claude Code configuration. Review what it changes.2. Check the author and repository.
3. the plugin does only what it claims.
A "code formatter" plugin should not need network access. A "security scanner" (like this one) should only need to read files and run grep — it should not be making external API calls or writing to your codebase. Match the plugin's claimed purpose against its actual capabilities.
4. Use Claude Code's safety features.
/sandbox to isolate file system and network access when e untrusted plugins.strictKnownMarketplaces in managed settings to control which marketplaces your team can use.5. Understand what protections do NOT exist today.
As of early 2026, the Claude Code plugin ecosystem does not have:
This will likely improve over time. But today, trust is entirely on you.
This plugin contains only two files that matter:
| File | What It Is | What to Check |
|---|---|---|
| skills/security-sweep/SKILL.md | The prompt that tells Claude how to run the scan | it only instructs Claude to read files and grep for patterns. No network calls, no writes, no exfiltration. |
| skills/security-sweep/patterns.md | Regex patterns for detecting | these are legitimate security patterns (OWASP, Semgrep, Gitleaks-derived). No obfuscated content. |
There are no hooks, no MCP servers, no scripts, no binaries. The allowed-tools in the skill frontmatter is restricted to Read, Grep, Glob, Bash, Agent — standard read-oriented tools.
You can this yourself in under 5 minutes. If you can't a plugin that quickly, that's a red flag about its complexity.
We are in an era where de increasingly rely on AI tools to write, review, and ship code. This creates a new category of attack surface:
npm install can run malicious postinstall scripts, installing a plugin loads prompts that change your AI's behaviorThe security community hasn't fully caught up with these risks yet. By using and sharing tools like this scanner, and by reading plugin source code before installing, you're part of building better practices.
---
| Module | What It Finds | Priority |
|---|---|---|
| Secrets | 30+ API key formats (AWS, GitHub, Stripe, OpenAI, Anthropic...), private keys, DB connection strings, committed .env files | Critical |
| Injection | SQL injection, XSS, command injection, SSRF, insecure deserialization, path tra | Critical |
| Auth | JWT misuse, weak password hashing, insecure cookies, broken access control | High |
| Config | CORS wildcards, DEBUG mode, exposed endpoints, TLS issues, Docker/K8s misconfig | High |
| Dependencies | Missing lockfiles, suspicious install scripts, supply chain red flags | High |
| AI | Hardcoded AI API keys, prompt injection , eval of LLM output, excessi permissions | High |
| Mobile | Android: cleartext traffic, exported components, insecure storage. iOS: ATS bypass, UserDefaults secrets | High |
| Data Exposure | PII in logs, sensitive data in URLs, plaintext HTTP, weak crypto | Medium |
Python, Ja/TypeScript, Ja, Go, Ruby, PHP, C#, Swift, Dart/Flutter — with framework-aware checks for Django, Flask, Express, Spring Boot, Next.js, React, Vue, Angular, and more.
The scan produces a structured report with:
Unlike regex-only tools, this skill le Claude's contextual understanding to:
Patterns are derived from:
Issues, PRs, and additional detection patterns are welcome. If you find a false positive or a missing class, open an issue.
MIT
开发语言:未知
Star 数:11
该项目属于安全软件方向的开源资源,代码结构清晰,适合安全研究人员学习参考。项目围绕Free Claude Code plugin that scans your project for leaked API keys, security holes, and common mistakes before you ship. No security expertise needed.展开,提供了可运行的实现,对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。
从技术实现角度看,此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论,梳理项目的初始化流程、核心模块职责与数据流转,逐步掌握其中的技术细节与设计思路。
1. 下载源码压缩包,解压到本地环境。
2. 根据项目类型准备对应的运行环境与依赖。
3. 按照 README 中的步骤完成配置与部署。
4. 在隔离的测试环境中运行验证,避免影响生产系统。
本资源来源于开源社区,仅供安全研究、技术学习与合法授权范围内的攻防演练使用,请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。
| 资源标题 | security-sweep-plugin - Free Claude Code plugin that scans your project fo |
| 所属分类 | 安全软件 |
| 发布作者 | admin |
| 发布时间 | 2026-10-05 23:02:00 |
| 下载权限 | 免费下载 |
| 附件数量 | 2 个下载链接 |
| 浏览次数 | 372 |
| 讨论数量 | 0 |
| 主题状态 | 正常讨论中 |