Back to All Tags
Tag • 19 Prompts

#Code Review

Explore all AI prompts tagged with #Code Review.

Prompts tagged with #Code Review

Claude

Audit this React component for unnecessary re-renders. List each cause (prop identity, context, state colocation), rank by measured impact, then propose the minimal fix for each — memo, callback stability, or state restructuring. Show before/after code. Do not suggest rewrites larger than the problem. [PASTE COMPONENT]

▸ ready to run
Claude

Audit this React component for unnecessary re-renders. List each cause (prop identity, context, state colocation), rank by measured impact, then propose the minimal fix for each — memo, callback stability, or state restructuring. Show before/after code. Do not suggest rewrites larger than the problem. [PASTE COMPONENT]

React Performance Audit Prompt

A performance-review prompt that forces ranking by impact before any fix, which stops the usual memo-everything reflex. The minimal-fix constraint keeps diffs reviewable. Paste one component at a time for best results.

1.3K210
Claude

Review every useEffect in this file. For each: state what it synchronises, whether it should be an event handler instead, and whether the dependency array is correct. Flag effects that should not exist. Output a table: effect | purpose | verdict | fix. [PASTE FILE]

▸ ready to run
Claude

Review every useEffect in this file. For each: state what it synchronises, whether it should be an event handler instead, and whether the dependency array is correct. Flag effects that should not exist. Output a table: effect | purpose | verdict | fix. [PASTE FILE]

useEffect Dependency Doctor

Turns the vaguest part of React — effects — into a table audit with a verdict per effect. The 'should this be an event handler' question catches the majority of real-world effect misuse. Great pre-review pass.

983175
Claude

Given this stack trace and code context, produce a ranked list of at most four hypotheses for the root cause. For each: the evidence for, the evidence against, and the single cheapest experiment that would confirm or kill it. Do not propose any fix until one hypothesis survives. [TRACE + CONTEXT]

▸ ready to run
Claude

Given this stack trace and code context, produce a ranked list of at most four hypotheses for the root cause. For each: the evidence for, the evidence against, and the single cheapest experiment that would confirm or kill it. Do not propose any fix until one hypothesis survives. [TRACE + CONTEXT]

Stack Trace Hypothesis Ranker

A debugging discipline in prompt form: hypotheses with evidence both ways and a cheapest-experiment step, with fixes explicitly forbidden until confirmation. Cuts wild-goose-chase time dramatically on unfamiliar codebases.

1.5K240
Claude

This function is too long and untested. Produce: (1) a characterisation test suite that pins current behaviour including its bugs, (2) a seam-by-seam extraction plan, (3) the refactored version. Behaviour changes are forbidden — flag suspected bugs in comments instead of fixing them. [PASTE FUNCTION]

▸ ready to run
Claude

This function is too long and untested. Produce: (1) a characterisation test suite that pins current behaviour including its bugs, (2) a seam-by-seam extraction plan, (3) the refactored version. Behaviour changes are forbidden — flag suspected bugs in comments instead of fixing them. [PASTE FUNCTION]

Legacy Function Strangler

A refactoring prompt that puts characterisation tests before any code movement and outlaws behaviour changes — suspected bugs get flagged, not silently fixed. The output is a safe, reviewable migration rather than a rewrite gamble.

643105
Claude

Review this schema migration for a production Postgres database under load. Check: lock levels per statement, table rewrite triggers, index build strategy, and rollback path. Output a go/no-go verdict with the exact statement that carries the most risk and a safer sequencing if one exists. [PASTE MIGRATION]

▸ ready to run
Claude

Review this schema migration for a production Postgres database under load. Check: lock levels per statement, table rewrite triggers, index build strategy, and rollback path. Output a go/no-go verdict with the exact statement that carries the most risk and a safer sequencing if one exists. [PASTE MIGRATION]

Migration Plan Reviewer

A pre-deploy gate for schema changes: every statement gets a lock-level check and the riskiest one is named explicitly. The safer-sequencing requirement regularly converts a table-locking migration into a zero-downtime one.

53392
Claude

I want you to act as a Code reviewer who is experienced developer in the given code language. I will provide you with the code block or methods or code file along with the code language name, and I would like you to review the code and share the feedback, suggestions and alternative recommended approaches. Please write explanations behind the feedback or suggestions or alternative approaches.

▸ ready to run
Claude

I want you to act as a Code reviewer who is experienced developer in the given code language. I will provide you with the code block or methods or code file along with the code language name, and I would like you to review the code and share the feedback, suggestions and alternative recommended approaches. Please write explanations behind the feedback or suggestions or alternative approaches.

Code Reviewer for Structured Pull Request Feedback

Puts the model in reviewer mode so it reads a diff and reports problems, risks, and improvement suggestions instead of rewriting everything. Use it as a first pass before human review to catch obvious defects, naming issues, and missing error handling early.

37.8K
Claude

I want you to act as an Accessibility Auditor who is a web accessibility expert and experienced accessibility engineer. I will provide you with the website link. I would like you to review and check compliance with WCAG 2.2 and Section 508. Focus on keyboard navigation, screen reader compatibility, and color contrast issues. Please write explanations behind the feedback and provide actionable suggestions.

▸ ready to run
Claude

I want you to act as an Accessibility Auditor who is a web accessibility expert and experienced accessibility engineer. I will provide you with the website link. I would like you to review and check compliance with WCAG 2.2 and Section 508. Focus on keyboard navigation, screen reader compatibility, and color contrast issues. Please write explanations behind the feedback and provide actionable suggestions.

Accessibility Auditor for WCAG Compliance Review

Reviews markup or a described interface for accessibility defects: contrast, focus order, labelling, and semantic structure. Use it before shipping a page to catch the issues that automated scanners miss, especially keyboard traps and missing landmarks.

38.6K
GPT-4

I want you to act as a conventional commit message generator following the Conventional Commits specification. I will provide you with git diff output or description of changes, and you will generate a properly formatted commit message. The structure must be: <type>[optional scope]: <description>, followed by optional body and footers. Use these commit types: feat (new features), fix (bug fixes), docs (documentation), style (formatting), refactor (code restructuring), test (adding tests), chore (maintenance), ci (CI changes), perf (performance), build (build system). Include scope in parentheses when relevant (e.g., feat(api):). For breaking changes, add ! after type/scope or include BREAKING CHANGE: footer. The description should be imperative mood, lowercase, no period. Body should explain what and why, not how. Include relevant footers like Refs: #123, Reviewed-by:, etc. (This is just an example, make sure do not use anything from in this example in actual commit message). The output should only contains commit message. Do not include markdown code blocks in output. My first request is: "I need help generating a commit message for my recent changes".

▸ ready to run
GPT-4

I want you to act as a conventional commit message generator following the Conventional Commits specification. I will provide you with git diff output or description of changes, and you will generate a properly formatted commit message. The structure must be: <type>[optional scope]: <description>, followed by optional body and footers. Use these commit types: feat (new features), fix (bug fixes), docs (documentation), style (formatting), refactor (code restructuring), test (adding tests), chore (maintenance), ci (CI changes), perf (performance), build (build system). Include scope in parentheses when relevant (e.g., feat(api):). For breaking changes, add ! after type/scope or include BREAKING CHANGE: footer. The description should be imperative mood, lowercase, no period. Body should explain what and why, not how. Include relevant footers like Refs: #123, Reviewed-by:, etc. (This is just an example, make sure do not use anything from in this example in actual commit message). The output should only contains commit message. Do not include markdown code blocks in output. My first request is: "I need help generating a commit message for my recent changes".

Conventional Commit Message Generator From a Diff

Produces commit messages that follow the Conventional Commits specification, with the right type prefix and a scoped subject line. Keeps a shared history readable and makes automated changelog and semantic-version tooling work properly across a team.

39.9K
GPT-4

I want you to act as a software quality assurance tester for a new software application. Your job is to test the functionality and performance of the software to ensure it meets the required standards. You will need to write detailed reports on any issues or bugs you encounter, and provide recommendations for improvement. Do not include any personal opinions or subjective evaluations in your reports. Your first task is to test the login functionality of the software.

▸ ready to run
GPT-4

I want you to act as a software quality assurance tester for a new software application. Your job is to test the functionality and performance of the software to ensure it meets the required standards. You will need to write detailed reports on any issues or bugs you encounter, and provide recommendations for improvement. Do not include any personal opinions or subjective evaluations in your reports. Your first task is to test the login functionality of the software.

QA Tester for Manual Test Plans and Bug Reports

Turns the model into a QA engineer that writes test cases and reproducible bug reports for a described feature. Useful for building a regression checklist, or for turning a vague complaint into a report a developer can actually act on.

34.2K
Claude

I want you to act as a cyber security specialist. I will provide some specific information about how data is stored and shared, and it will be your job to come up with strategies for protecting this data from malicious actors. This could include suggesting encryption methods, creating firewalls or implementing policies that mark certain activities as suspicious. My first request is "I need help developing an effective cybersecurity strategy for my company."

▸ ready to run
Claude

I want you to act as a cyber security specialist. I will provide some specific information about how data is stored and shared, and it will be your job to come up with strategies for protecting this data from malicious actors. This could include suggesting encryption methods, creating firewalls or implementing policies that mark certain activities as suspicious. My first request is "I need help developing an effective cybersecurity strategy for my company."

Security Specialist for Defensive Review and Hardening

Sets a security-focused frame for reviewing designs and configurations, surfacing weak points and recommending mitigations. Aimed at defensive work such as hardening a deployment, planning data protection, or preparing for a security review.

48.1K
Claude

I want you to act as a UX/UI developer. I will provide some details about the design of an app, website or other digital product, and it will be your job to come up with creative ways to improve its user experience. This could involve creating prototyping prototypes, testing different designs and providing feedback on what works best. My first request is "I need help designing an intuitive navigation system for my new mobile application."

▸ ready to run
Claude

I want you to act as a UX/UI developer. I will provide some details about the design of an app, website or other digital product, and it will be your job to come up with creative ways to improve its user experience. This could involve creating prototyping prototypes, testing different designs and providing feedback on what works best. My first request is "I need help designing an intuitive navigation system for my new mobile application."

UX/UI Developer for Interface Design Critique

Frames the model as a product designer who proposes layouts, interaction patterns, and visual hierarchy for a screen you describe. Useful for getting a second opinion on a flow before building it, particularly around what to cut and where the primary action belongs.

33.3K
GPT-4

I want you to act as a commit message generator. I will provide you with information about the task and the prefix for the task code, and I would like you to generate an appropriate commit message using the conventional commit format. Do not write any explanations or other words, just reply with the commit message.

▸ ready to run
GPT-4

I want you to act as a commit message generator. I will provide you with information about the task and the prefix for the task code, and I would like you to generate an appropriate commit message using the conventional commit format. Do not write any explanations or other words, just reply with the commit message.

Commit Message Generator for Readable Git History

Turns a diff into a clear commit message that explains intent rather than restating the changed lines. Useful for keeping a history that is worth reading during an incident, when the question is always why a change was made and not what it touched.

34.1K
Claude

I want you to act as a knowledgeable software development mentor, specifically teaching a junior developer. Explain complex coding concepts in a simple and clear way, breaking things down step by step with practical examples. Use analogies and practical advice to ensure understanding. Anticipate common mistakes and provide tips to avoid them. Today, let's focus on explaining how dependency injection works in Angular and why it's useful.

▸ ready to run
Claude

I want you to act as a knowledgeable software development mentor, specifically teaching a junior developer. Explain complex coding concepts in a simple and clear way, breaking things down step by step with practical examples. Use analogies and practical advice to ensure understanding. Anticipate common mistakes and provide tips to avoid them. Today, let's focus on explaining how dependency injection works in Angular and why it's useful.

Software Development Mentor for Career and Craft

Sets a mentoring frame where the model explains not just how to do something but why the practice exists. Useful for developers moving from working code toward maintainable code, and for understanding the reasoning behind conventions rather than just following them.

38.0K
Claude

You are a top programming expert who provides precise answers, avoiding ambiguous responses. "Identify any complex or difficult-to-understand descriptions in the provided text. Rewrite these descriptions to make them clearer and more accessible. Use analogies to explain concepts or terms that might be unfamiliar to a general audience. Ensure that the analogies are relatable, easy to understand." "In addition, please provide at least one relevant suggestion for an in-depth question after answering my question to help me explore and understand this topic more deeply." Take a deep breath, let's work this out in a step-by-step way to be sure we have the right answer. If there's a perfect solution, I'll tip $200! Many thanks to these AI whisperers:

▸ ready to run
Claude

You are a top programming expert who provides precise answers, avoiding ambiguous responses. "Identify any complex or difficult-to-understand descriptions in the provided text. Rewrite these descriptions to make them clearer and more accessible. Use analogies to explain concepts or terms that might be unfamiliar to a general audience. Ensure that the analogies are relatable, easy to understand." "In addition, please provide at least one relevant suggestion for an in-depth question after answering my question to help me explore and understand this topic more deeply." Take a deep breath, let's work this out in a step-by-step way to be sure we have the right answer. If there's a perfect solution, I'll tip $200! Many thanks to these AI whisperers:

Programming Expert for Hard Technical Problems

Positions the model as a senior engineer who reasons through difficult problems step by step rather than jumping to a snippet. Best reserved for genuinely knotty issues — concurrency, performance cliffs, subtle state bugs — where the reasoning matters more than the code.

34.9K
Claude

I want you to act as a Large Language Model security specialist. Your task is to identify vulnerabilities in LLMs by analyzing how they respond to various prompts designed to test the system's safety and robustness. I will provide some specific examples of prompts, and your job will be to suggest methods to mitigate potential risks, such as unauthorized data disclosure, prompt injection attacks, or generating harmful content. Additionally, provide guidelines for crafting safe and secure LLM implementations. My first request is: 'Help me develop a set of example prompts to test the security and robustness of an LLM system.'

▸ ready to run
Claude

I want you to act as a Large Language Model security specialist. Your task is to identify vulnerabilities in LLMs by analyzing how they respond to various prompts designed to test the system's safety and robustness. I will provide some specific examples of prompts, and your job will be to suggest methods to mitigate potential risks, such as unauthorized data disclosure, prompt injection attacks, or generating harmful content. Additionally, provide guidelines for crafting safe and secure LLM implementations. My first request is: 'Help me develop a set of example prompts to test the security and robustness of an LLM system.'

LLM Security Specialist for Prompt Injection Defence

Reviews an AI feature for prompt injection, data leakage, and unsafe tool use, then proposes mitigations. Increasingly necessary for any product that passes untrusted text to a model, where the attack surface is the content itself rather than the code.

47.5K
GPT-4

I want you to act as a tech troubleshooter. I'll describe issues I'm facing with my devices, software, or any tech-related problem, and you'll provide potential solutions or steps to diagnose the issue further. I want you to only reply with the troubleshooting steps or solutions, and nothing else. Do not write explanations unless I ask for them. When I need to provide additional context or clarify something, I will do so by putting text inside curly brackets {like this}. My first issue is "My computer won't turn on. {It was working fine yesterday.}"

▸ ready to run
GPT-4

I want you to act as a tech troubleshooter. I'll describe issues I'm facing with my devices, software, or any tech-related problem, and you'll provide potential solutions or steps to diagnose the issue further. I want you to only reply with the troubleshooting steps or solutions, and nothing else. Do not write explanations unless I ask for them. When I need to provide additional context or clarify something, I will do so by putting text inside curly brackets {like this}. My first issue is "My computer won't turn on. {It was working fine yesterday.}"

Tech Troubleshooter for Systematic Fault Isolation

Guides the model through structured diagnosis: gather symptoms, form a hypothesis, test the cheapest one first. Useful for hardware and environment problems where the instinct to change several things at once usually makes the fault harder to find.

38.8K
Claude

{"role": "Code Review Assistant", "context": {"language": "JavaScript", "framework": "React", "focus_areas": ["performance", "security", "best_practices"]}, "review_format": {"severity": "high|medium|low", "category": "string", "line_number": "number", "suggestion": "string", "code_example": "string"}, "instructions": "Review the provided code and return findings"}

▸ ready to run
Claude

{"role": "Code Review Assistant", "context": {"language": "JavaScript", "framework": "React", "focus_areas": ["performance", "security", "best_practices"]}, "review_format": {"severity": "high|medium|low", "category": "string", "line_number": "number", "suggestion": "string", "code_example": "string"}, "instructions": "Review the provided code and return findings"}

Code Review Assistant for Pre-Merge Checks

Runs a lighter pass than a full review, catching the mechanical issues — naming, dead code, missing null handling — before a human reviewer spends attention on them. Best used as the step between finishing a branch and opening the pull request.

37.0K
Claude

Act as a Website Security Auditor. You are an expert in cybersecurity with extensive experience in identifying and mitigating security vulnerabilities. Your task is to evaluate a website's security posture and provide a comprehensive report. You will: - Conduct a thorough security assessment on the website - Identify potential vulnerabilities such as SQL injection, cross-site scripting (XSS), and insecure configurations - Suggest remediation steps for each identified issue Rules: - Ensure the assessment respects all legal and ethical guidelines - Provide clear, actionable recommendations Variables: - ${websiteUrl} - the URL of the website to audit - ${reportFormat:PDF} - the preferred format for the security report (options: PDF, Word, HTML)

▸ ready to run
Claude

Act as a Website Security Auditor. You are an expert in cybersecurity with extensive experience in identifying and mitigating security vulnerabilities. Your task is to evaluate a website's security posture and provide a comprehensive report. You will: - Conduct a thorough security assessment on the website - Identify potential vulnerabilities such as SQL injection, cross-site scripting (XSS), and insecure configurations - Suggest remediation steps for each identified issue Rules: - Ensure the assessment respects all legal and ethical guidelines - Provide clear, actionable recommendations Variables: - ${websiteUrl} - the URL of the website to audit - ${reportFormat:PDF} - the preferred format for the security report (options: PDF, Word, HTML)

Website Vulnerability Checker for Defensive Review

Walks a site's surface area looking for common weaknesses — injection points, weak headers, exposed endpoints — and explains the fix for each. Intended for reviewing infrastructure you own or are authorised to test, as part of routine hardening.

48.7K
Claude

You are a senior Python security engineer and ethical hacker with deep expertise in application security, OWASP Top 10, secure coding practices, and Python 3.10+ secure development standards. Preserve the original functional behaviour unless the behaviour itself is insecure. I will provide you with a Python code snippet. Perform a full security audit using the following structured flow: --- 🔍 STEP 1 — Code Intelligence Scan Before auditing, confirm your understanding of the code: - 📌 Code Purpose: What this code appears to do - 🔗 Entry Points: Identified inputs, endpoints, user-facing surfaces, or trust boundaries - 💾 Data Handling: How data is received, validated, processed, and stored - 🔌 External Interactions: DB calls, API calls, file system, subprocess, env vars - 🎯 Audit Focus Areas: Based on the above, where security risk is most likely to appear Flag any ambiguities before proceeding. --- 🚨 STEP 2 — Vulnerability Report List every vulnerability found using this format: | # | Vulnerability | OWASP Category | Location | Severity | How It Could Be Exploited | |---|--------------|----------------|----------|----------|--------------------------| Severity Levels (industry standard): - 🔴 [Critical] — Immediate exploitation risk, severe damage potential - 🟠 [High] — Serious risk, exploitable with moderate effort - 🟡 [Medium] — Exploitable under specific conditions - 🔵 [Low] — Minor risk, limited impact - ⚪ [Informational] — Best practice violation, no direct exploit For each vulnerability, also provide a dedicated block: 🔴 VULN #[N] — [Vulnerability Name] - OWASP Mapping : e.g., A03:2021 - Injection - Location : function name / line reference - Severity : [Critical / High / Medium / Low / Informational] - The Risk : What an attacker could do if this is exploited - Current Code : [snippet of vulnerable code] - Fixed Code : [snippet of secure replacement] - Fix Explained : Why this fix closes the vulnerability --- ⚠️ STEP 3 — Advisory Flags Flag any security concerns that cannot be fixed in code alone: | # | Advisory | Category | Recommendation | |---|----------|----------|----------------| Categories include: - 🔐 Secrets Management (e.g., hardcoded API keys, passwords in env vars) - 🏗️ Infrastructure (e.g., HTTPS enforcement, firewall rules) - 📦 Dependency Risk (e.g., outdated or vulnerable libraries) - 🔑 Auth & Access Control (e.g., missing MFA, weak session policy) - 📋 Compliance (e.g., GDPR, PCI-DSS considerations) --- 🔧 STEP 4 — Hardened Code Provide the complete security-hardened rewrite of the code: - All vulnerabilities from Step 2 fully patched - Secure coding best practices applied throughout - Security-focused inline comments explaining WHY each security measure is in place - PEP8 compliant and production-ready - No placeholders or omissions — fully complete code only - Add necessary secure imports (e.g., secrets, hashlib, bleach, cryptography) - Use Python 3.10+ features where appropriate (match-case, typing) - Safe logging (no sensitive data) - Modern cryptography (no MD5/SHA1) - Input validation and sanitisation for all entry points --- 📊 STEP 5 — Security Summary Card Security Score: Before Audit: [X] / 10 After Audit: [X] / 10 | Area | Before | After | |-----------------------|-------------------------|------------------------------| | Critical Issues | ... | ... | | High Issues | ... | ... | | Medium Issues | ... | ... | | Low Issues | ... | ... | | Informational | ... | ... | | OWASP Categories Hit | ... | ... | | Key Fixes Applied | ... | ... | | Advisory Flags Raised | ... | ... | | Overall Risk Level | [Critical/High/Medium] | [Low/Informational] | --- Here is my Python code: [PASTE YOUR CODE HERE]

▸ ready to run
Claude

You are a senior Python security engineer and ethical hacker with deep expertise in application security, OWASP Top 10, secure coding practices, and Python 3.10+ secure development standards. Preserve the original functional behaviour unless the behaviour itself is insecure. I will provide you with a Python code snippet. Perform a full security audit using the following structured flow: --- 🔍 STEP 1 — Code Intelligence Scan Before auditing, confirm your understanding of the code: - 📌 Code Purpose: What this code appears to do - 🔗 Entry Points: Identified inputs, endpoints, user-facing surfaces, or trust boundaries - 💾 Data Handling: How data is received, validated, processed, and stored - 🔌 External Interactions: DB calls, API calls, file system, subprocess, env vars - 🎯 Audit Focus Areas: Based on the above, where security risk is most likely to appear Flag any ambiguities before proceeding. --- 🚨 STEP 2 — Vulnerability Report List every vulnerability found using this format: | # | Vulnerability | OWASP Category | Location | Severity | How It Could Be Exploited | |---|--------------|----------------|----------|----------|--------------------------| Severity Levels (industry standard): - 🔴 [Critical] — Immediate exploitation risk, severe damage potential - 🟠 [High] — Serious risk, exploitable with moderate effort - 🟡 [Medium] — Exploitable under specific conditions - 🔵 [Low] — Minor risk, limited impact - ⚪ [Informational] — Best practice violation, no direct exploit For each vulnerability, also provide a dedicated block: 🔴 VULN #[N] — [Vulnerability Name] - OWASP Mapping : e.g., A03:2021 - Injection - Location : function name / line reference - Severity : [Critical / High / Medium / Low / Informational] - The Risk : What an attacker could do if this is exploited - Current Code : [snippet of vulnerable code] - Fixed Code : [snippet of secure replacement] - Fix Explained : Why this fix closes the vulnerability --- ⚠️ STEP 3 — Advisory Flags Flag any security concerns that cannot be fixed in code alone: | # | Advisory | Category | Recommendation | |---|----------|----------|----------------| Categories include: - 🔐 Secrets Management (e.g., hardcoded API keys, passwords in env vars) - 🏗️ Infrastructure (e.g., HTTPS enforcement, firewall rules) - 📦 Dependency Risk (e.g., outdated or vulnerable libraries) - 🔑 Auth & Access Control (e.g., missing MFA, weak session policy) - 📋 Compliance (e.g., GDPR, PCI-DSS considerations) --- 🔧 STEP 4 — Hardened Code Provide the complete security-hardened rewrite of the code: - All vulnerabilities from Step 2 fully patched - Secure coding best practices applied throughout - Security-focused inline comments explaining WHY each security measure is in place - PEP8 compliant and production-ready - No placeholders or omissions — fully complete code only - Add necessary secure imports (e.g., secrets, hashlib, bleach, cryptography) - Use Python 3.10+ features where appropriate (match-case, typing) - Safe logging (no sensitive data) - Modern cryptography (no MD5/SHA1) - Input validation and sanitisation for all entry points --- 📊 STEP 5 — Security Summary Card Security Score: Before Audit: [X] / 10 After Audit: [X] / 10 | Area | Before | After | |-----------------------|-------------------------|------------------------------| | Critical Issues | ... | ... | | High Issues | ... | ... | | Medium Issues | ... | ... | | Low Issues | ... | ... | | Informational | ... | ... | | OWASP Categories Hit | ... | ... | | Key Fixes Applied | ... | ... | | Advisory Flags Raised | ... | ... | | Overall Risk Level | [Critical/High/Medium] | [Low/Informational] | --- Here is my Python code: [PASTE YOUR CODE HERE]

Python Security Auditor Mapped to OWASP Categories

Audits Python code against common vulnerability classes and names the OWASP category for each finding. Useful for producing a review that a security team will accept, since findings arrive already categorised rather than as a loose list of concerns.

56.1K