# JS Libraries

> Use when auditing slow page loads, heavy assets, or rendering delays related to Use secure and up-to-date JS libraries. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

- Skill: `thedaviddias/js-libraries` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add thedaviddias/js-libraries`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thedaviddias/js-libraries/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: thedaviddias (https://skillmd.com/u/thedaviddias)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/thedaviddias/js-libraries

---


# Use secure and up-to-date JS libraries

Outdated or vulnerable libraries pose security risks and often include unnecessary bloat that degrades performance.

## Quick Reference

- Regularly audit dependencies for known security vulnerabilities
- Replace heavy libraries with lightweight alternatives (e.g., date-fns vs moment)
- Ensure libraries are properly versioned and served via reliable CDNs or self-hosted

## Check

Check the project's JavaScript dependencies for known vulnerabilities and outdated versions.

## Fix

Update vulnerable libraries to secure versions and replace bloated dependencies with modern, lightweight alternatives.

## Explain

Explain the risks of using outdated JavaScript libraries and the benefits of using lightweight alternatives.

## Code Review

Review the routes, assets, and loading behavior that affect Use secure and up-to-date JS libraries. Flag exact files, requests, or rendering steps that add unnecessary network, CPU, or layout cost, and describe the measurement method used to confirm the issue.

---

For full implementation details, code examples, and framework-specific guidance,
see `references/rule.md`.

Rule page: https://frontendchecklist.io/en/rules/performance/js-libraries