javascript-vulnerable-outdated-components

A set of security rules for finding vulnerable or outdated JavaScript libraries and components in web projects.

In plain words
What is it for?
It checks files such as package.json, HTML, JavaScript, and related source files for outdated packages, unsafe CDN usage, hardcoded library versions, and deprecated APIs.
Why use it?
It alerts developers to dependency versions, external scripts, and Node.js APIs that may introduce known security or maintenance risks.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/ivangrynenko/cursorrules/javascript-vulnerable-outdated-components
Clone the repo
git clone --depth 1 https://github.com/ivangrynenko/cursorrules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,368 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03368
Opus 5 $0.00000 $0.01684
Sonnet 5 $0.00000 $0.00674
Haiku 4.5 $0.00000 $0.00337

Measured yesterday against content hash 96dcba0896f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

javascript-vulnerable-outdated-components scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/rules/javascript-vulnerable-outdated-components.mdc · 337 lines

How it starts

The opening of the file, as written. The whole thing — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.

JavaScript Vulnerable and Outdated Components (OWASP A06:2021)

actions:

  • type: enforce conditions:

    Pattern 1: Outdated Package Versions in package.json

    • pattern: ""(dependencies|devDependencies)"\s*:\s*\{[^}]?"([^"]+)"\s:\s*"\^?([0-9]+\.[0-9]+\.[0-9]+)"" location: "package\.json$" message: "Check for outdated dependencies in package.json. Regularly update dependencies to avoid known vulnerabilities."
    • pattern: "<script\s+src=['"]https?://(?:cdn|unpkg|jsdelivr)[^'"]['"][^>](?!integrity=)" location: "\.(html|js|jsx|ts|tsx)$" message: "CDN resources without integrity hashes. Add integrity and crossorigin attributes to script tags loading external resources."

    Pattern 3: Hardcoded Library Versions in HTML

    • pattern: "<script\s+src=['"][^'"](?:jquery|bootstrap|react|vue|angular|lodash|moment)[@-][0-9]+\.[0-9]+\.[0-9]+[^'"]['"]" location: "\.html$" message: "Hardcoded library versions in HTML. Consider using a package manager to manage dependencies."

    Pattern 4: Deprecated Node.js APIs

    • pattern: "(?:new Buffer\(|require\(['"]crypto['"]\)\.createCipher\(|require\(['"]crypto['"]\)\.randomBytes\([^,)]+\)|require\(['"]fs['"]\)\.exists\()" message: "Using deprecated Node.js APIs. Replace with modern alternatives to avoid security and maintenance issues."

    Pattern 5: Deprecated Browser APIs

    • pattern: "document\.write\(|document\.execCommand\(|escape\(|unescape\(|showModalDialog\(|localStorage\.clear\(\)|sessionStorage\.clear\(\)" location: "(?:src|components|pages)" message: "Using deprecated browser APIs. Replace with modern alternatives to avoid compatibility and security issues."

    Pattern 6: Insecure Dependency Loading

    • pattern: "require\([^)]?\+\s[^)]+\)|import\([^)]?\+\s[^)]+\)" message: "Dynamic dependency loading with variable concatenation. This can lead to dependency confusion attacks."

    Pattern 7: Vulnerable Regular Expression Patterns (ReDoS)

    • pattern: "new RegExp\([^)]?(?:\(.\)\|\\+|\+\*|\{\d+,\})" message: "Potentially vulnerable regular expression pattern that could lead to ReDoS attacks. Review and optimize the regex pattern."

    Pattern 8: Insecure Package Installation

    • pattern: "npm\s+install\s+(?:--no-save|--no-audit|--no-fund|--force)" location: "(?:scripts|Dockerfile|docker-compose\.yml|\.github/workflows)" message: "Insecure package installation flags. Avoid using --no-audit, --no-save, or --force flags when installing packages."

    Pattern 9: Missing Lock Files

    • pattern: "package\.json" location: "package\.json$" negative_pattern: "package-lock\.json|yarn\.lock|pnpm-lock\.yaml" message: "Missing lock file. Use package-lock.json, yarn.lock, or pnpm-lock.yaml to ensure dependency consistency."

    Pattern 10: Insecure Webpack Configuration

    • pattern: "webpack\.config\.js" location: "webpack\.config\.js$" negative_pattern: "(?:noEmitOnErrors|optimization\.minimize)" message: "Potentially insecure webpack configuration. Consider enabling noEmitOnErrors and optimization.minimize."

    Pattern 11: Outdated TypeScript Configuration

    • pattern: ""compilerOptions"\s*:\s*\{[^}]?"target"\s:\s*"ES5"" location: "tsconfig\.json$" message: "Outdated TypeScript target. Consider using a more modern target like ES2020 for better security features."

    Pattern 12: Insecure Package Sources

    • pattern: "registry\s*=\s*(?!https://registry\\.npmjs\\.org)" location: "\.npmrc$" message: "Using a non-standard npm registry. Ensure you trust the source of your packages."

Read the full file on GitHub · 337 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 337 lines · 3,368 tokens per session scan A 96dcba0896f9

Subscribe to this mod's changes

javascript-vulnerable-outdated-components is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (87 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,368 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.