fix: replace broken npmjs.org links with npmjs.com in README

[Copilot]

User description

The scheduled Links Checker CI was failing due to https://www.npmjs.org/package/agent-rules returning 403 Forbidden. The .org domain is not the canonical npm registry — .com is.

Changes

• README.md: Updated 3 npm badge anchor hrefs from npmjs.org → npmjs.com

- <a href="https://www.npmjs.org/package/agent-rules">
+ <a href="https://www.npmjs.com/package/agent-rules">

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

---

PR Type

Bug fix

---

Description

• Replace broken npmjs.org links with npmjs.com domain

• Fix 3 npm package badge hrefs in README

• Resolve Links Checker CI failures from 403 errors

---

Diagram Walkthrough

flowchart LR
  A["npmjs.org links<br/>403 Forbidden"] -- "update domain" --> B["npmjs.com links<br/>canonical registry"]
  B -- "fixes" --> C["Links Checker CI<br/>passing"]

Loading

File Walkthrough

	Relevant files
Bug fix	README.md Update npm registry domain in badges                                          README.md Updated 3 npm package badge anchor hrefs from npmjs.org to npmjs.com Affected badges: version, license, and downloads Resolves broken links causing CI failures +3/-3

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.