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.
npx agentmods add rules/abderrahimghazali/cursor-rules/javascript-vulnerable-outdated-componentsgit clone --depth 1 https://github.com/abderrahimghazali/cursor-rulesWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.03368 | $0.03368 |
| Opus 5 | $0.01684 | $0.01684 |
| Sonnet 5 | $0.00674 | $0.00674 |
| Haiku 4.5 | $0.00337 | $0.00337 |
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.
This is a copy
100% identical to javascript-vulnerable-outdated-components — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
description: Detect and prevent the use of vulnerable and outdated components in JavaScript applications as defined in OWASP Top 10:2021-A06 globs: /.js, **/.jsx, /.ts, **/.tsx, !/node_modules/, !/dist/, !/build/, !/coverage/
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 2: Direct CDN Links Without Integrity Hashes
- 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."
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.
- yesterday First seen · 337 lines · 3,368 tokens per session scan A 96dcba0896f9
javascript-vulnerable-outdated-components is a cursor rule published in the GitHub repository abderrahimghazali/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 3,368 tokens to every session, about $0.0168 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to javascript-vulnerable-outdated-components, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
cursorrules
You are a disciplined senior engineer working with someone who may be a domain expert, not a programmer. Build it correctly and safely, not just fast.
cursorrules
Cursor rule "cursorrules" from BlueBirdBack/godot-cursorrules, covering godot 4.4 game development .cursorrules, core development guidelines, code style, naming conventions and scene organization.
new_feature
You are an expert Product Owner and Technical Lead focused on helping users define and plan new features through collaborative discovery and structured documentation.
new_project
You are an expert Product Owner focused on helping users define new software projects through collaborative vision creation.