Skip to content
Skills Library
Security · Review & audit

safe-function-lint

/safe-function-lint

Scan Python or React/JS code for outdated, banned, or vulnerable functions/methods (eval, pickle.loads, subprocess shell=True, dangerouslySetInnerHTML, md5 for passwords, etc.) and propose the exact safe alternative for each hit. Use when reviewing a diff/PR, before a commit, or when the user asks "is this function safe", "any vulnerable functions here", or wants a secure-coding pass on Python or React code.

Licence
GPL-3.0
Last repository change
07.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.08.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Scan Python or React/JS code for outdated, banned, or vulnerable functions/methods (eval, pickle.loads, subprocess shell=True, dangerouslySetInnerHTML, md5 for passwords, etc.) and propose the exact safe alternative for each hit. Use when reviewing a diff/PR, before a commit, or when the user asks "is this function safe", "any vulnerable functions here", or wants a secure-coding pass on Python or React code.

Triggers from the description

is this function safeany vulnerable functions here
Original author description

Scan Python or React/JS code for outdated, banned, or vulnerable functions/methods (eval, pickle.loads, subprocess shell=True, dangerouslySetInnerHTML, md5 for passwords, etc.) and propose the exact safe alternative for each hit. Use when reviewing a diff/PR, before a commit, or when the user asks "is this function safe", "any vulnerable functions here", or wants a secure-coding pass on Python or React code.

How it works

SKILL.md has no level-two headings · 37 lines, 240 words

SKILL.md preview
---
name: safe-function-lint
description: Scan Python or React/JS code for outdated, banned, or vulnerable functions/methods (eval, pickle.loads, subprocess shell=True, dangerouslySetInnerHTML, md5 for passwords, etc.) and propose the exact safe alternative for each hit. Use when reviewing a diff/PR, before a commit, or when the user asks "is this function safe", "any vulnerable functions here", or wants a secure-coding pass on Python or React code.
---

# Goal

For a given diff, file, or directory, find every use of a banned/outdated/vulnerable
function or API in Python or React/JS, and for each hit report: the exact standard it
violates, why it's risky, and the concrete safe replacement — never just "this is bad."

# Steps

1. Determine scope: staged diff (`git diff --cached`) by default if inside a git repo
   and no path is given; otherwise the path/files the user named.
2. Identify language(s) present (`.py` → Python rules; `.js/.jsx/.ts/.tsx` → React/JS rules).
3. Load `reference.md` in this skill directory — it is the rule pack (CWE/OWASP ASVS
   cited, matcher pattern, safe alternative) — and check the scoped code against it.
4. If Semgrep is installed, prefer running it for precision:
   ```
   semgrep --config "$CLAUDE_PLUGIN_ROOT/rules/semgrep-python.yml" <path>   # Python
   semgrep --config "$CLAUDE_PLUGIN_ROOT/rules/semgrep-react.yml" <path>   # React/JS
   ```
   If Semgrep isn't installed, fall back to manually pattern-matching against `reference.md`
   directly — do not skip the check, degrade to manual review instead.
5. De-duplicate and rank findings by severity (Critical/High/Medium/Low, per `reference.md`).

# Output

For each finding, report in this exact shape:

```
[<severity>] <file>:<line> — <banned function/pattern>
Standard: <CWE-ID / OWASP ASVS section>
Risk: <one sentence — what breaks and how it's exploited>
Fix: <exact safe replacement, as a code snippet if it's not a 1:1 rename>
```

Close with a one-line summary count by severity. Do not restate the whole file — only
the offending lines and their fixes.
Files in this package (2)
  • SKILL.md 2 KB
  • reference.md 6 KB

Versions

The database has no other skills named safe-function-lint.

Database snapshot: 13.11.2026 · package version 7a30884248c8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100dependency-vuln-scanner
    Scan a .NET project's NuGet dependencies for known vulnerabilities, deprecated/outdated packages, and transitive risks, then recommend safe upgrades. Use this skill whenever the user wants to check dependencies for CVEs, vulnerable packages, outdated NuGet, transitive…
  • 100codeguard
    Secure code reviewer for JavaScript, TypeScript and Python. Use this whenever the user asks to review code for vulnerabilities, or when a vigilsutra audit reports VS-CODE findings (eval, shell injection, SQL built from strings, unsafe pickle or YAML, disabled TLS verification,…
  • 100scan-code
    Scans a Power Pages site project for security issues in source code and dependencies. Runs static analysis and dependency scanning, then surfaces findings by category (code patterns, vulnerable packages, secrets, license issues). Use when the user wants to review code for…
  • 84audit-dependencies
    Audit project dependencies for security vulnerabilities and outdated packages, then apply safe updates. Use when user says "audit my dependencies", "check for vulnerable packages", "run npm audit", "find security issues in my packages", "what packages are outdated", "update my…
  • 95orbitant-owasp-scan
    Use when scanning a Node.js or Python repo for OWASP Top 10 vulnerabilities — hardcoded secrets, SQL injection patterns, weak cryptography, dangerous functions (eval, exec, shell=True), missing security headers, or dependency lockfile issues. Activates when someone asks about…
  • 100safe-c-functions
    Apply when reviewing or writing C/C++ code that uses memory or string operations. Identifies banned functions, provides safe replacements, compiler hardening flags, and refactoring examples.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.