Merge pull request #353 from ejarocki-cloudlinux/master

add requirejs page

Author: ejarocki-cloudlinux

docs/.vuepress/components/ELSTechnology.vue

@@ -500,6 +500,11 @@ const techData = [
         versions: "7.5.1",
         link: "./react-router/",
       },
+      {
+        name: "RequireJS",
+        versions: "2.3.6",
+        link: "./requirejs/",
+      },
       {
         name: "Request",
         versions: "2.88.0",

docs/.vuepress/config-client/sidebar.ts

@@ -315,6 +315,10 @@ export default {
                     path: '/els-for-libraries/react-router/',
                     icon: '/images/react-logo.webp',
                 },
+                {
+                    path: '/els-for-libraries/requirejs/',
+                    icon: '/images/requirejs-logo.webp',
+                },
                 {
                     path: '/els-for-libraries/tailwindcss/',
                     icon: '/images/tailwindcss-logo.webp',

docs/.vuepress/public/images/requirejs-logo.webp

@@ -0,0 +1,185 @@
+# RequireJS
+
+Endless Lifecycle Support (ELS) for RequireJS from TuxCare provides security fixes for RequireJS versions that have reached their end of life. This allows you to continue running RequireJS applications without vulnerability concerns, even after official support has ended.
+
+## Supported RequireJS Versions
+
+* RequireJS 2.3.6
+
+## Connection to ELS for RequireJS Library
+
+This guide outlines the steps needed to integrate the TuxCare ELS for the RequireJS library.
+
+## Step 1: Get Token
+
+You need a token in order to use TuxCare ELS RequireJS library. Anonymous access is disabled. To receive the token, please contact [[email protected]](mailto:[email protected]).
+
+## Step 2: Set Up ELS for RequireJS
+
+TuxCare provides ELS for RequireJS as an NPM package, hosted on a secure internal registry. Follow the steps below to add it to your project and get started.
+
+1. Navigate to the root directory of your RequireJS project.
+2. Create a `.npmrc` file or update it if it already exists.
+
+   **Example:**
+
+   ```text
+   my-requirejs-project/
+   ├── node_modules/
+   ├── package.json
+   ├── .npmrc         ⚠️ ← Create it here
+   └── package-lock.json
+   ```
+
+3. Use an editor of your choice (e.g., VS Code) to add the following registry address line:
+
+   <CodeWithCopy>
+
+   ```text
+   registry=https://registry.npmjs.org/
+   @els-js:registry=https://nexus.repo.tuxcare.com/repository/els_js/
+   //nexus.repo.tuxcare.com/repository/els_js/:_auth=${TOKEN}
+   ```
+
+   </CodeWithCopy>
+
+   :::warning
+   Replace ${TOKEN} with the token you received from [[email protected]](mailto:[email protected]).
+   :::
+
+4. Update your `package.json` file to replace your RequireJS dependencies with the TuxCare packages. You can do this in two ways:
+
+   * **Option 1: TuxCare Patcher (Automated)**
+
+     Install the Patcher globally and run it. The TuxCare Patcher automatically detects the RequireJS version in your `package.json` and updates your `dependencies` and `overrides` to use the corresponding TuxCare `@els-js/*` packages.
+
+     <CodeWithCopy>
+
+     ```text
+     npm install -g @els-js/tuxcare-patcher --userconfig ./.npmrc
+     tuxcare-patch-js
+     ```
+
+     </CodeWithCopy>
+
+     The patcher will update your `package.json`, for example, from:
+
+     ```text
+     "dependencies": {
+       "requirejs": "^2.3.6"
+     }
+     ```
+
+     to:
+
+     ```text
+     "dependencies": {
+       "requirejs": "npm:@els-js/[email protected]"
+     },
+     "overrides": {
+       "[email protected]": "npm:@els-js/[email protected]"
+     }
+     ```
+    
+   * **Option 2: Manual Update**
+
+     Manually update your `package.json` file by replacing your RequireJS dependencies with the TuxCare packages. This method gives you full control over which packages to update.
+
+     <CodeWithCopy>
+
+     ```text
+     "dependencies": {
+       "requirejs": "npm:@els-js/[email protected]"
+     }
+     ```
+
+     </CodeWithCopy>
+
+5. You need to remove the `node_modules` directory and the `package-lock.json` file, and also clear the `npm cache` before installing the patched packages. Use the following commands:
+   
+   <CodeWithCopy>
+
+   ```text
+   rm -rf node_modules package-lock.json && npm cache clean --force
+   ```
+
+   </CodeWithCopy>
+
+6. Run the following command to install the ELS version of the RequireJS library (token for the TuxCare repository will be automatically picked up from your `.npmrc` file):
+
+   <CodeWithCopy>
+
+   ```text
+   npm install
+   ```
+
+   </CodeWithCopy>
+
+   You will see an output like:
+
+   ```text
+    added 1 package, and audited 2 packages in 792ms
+    
+    found 0 vulnerabilities
+   ```
+
+7. You've successfully installed the Tuxcare ELS version of the RequireJS library into your project.
+
+## Vulnerability Exploitability eXchange (VEX) 
+
+VEX is a machine-readable format that tells you if a known vulnerability and is actually exploitable in your product. It reduces false positives, helps prioritize real risks.
+
+TuxCare provides VEX for RequireJS ELS versions: [security.tuxcare.com/vex/cyclonedx/els_lang_javascript/requirejs/](https://security.tuxcare.com/vex/cyclonedx/els_lang_javascript/requirejs/).
+
+## How to Upgrade to a Newer Version of TuxCare Packages
+
+If you have already installed a package with a `tuxcare.1` suffix and want to upgrade to a newer release (for example, `tuxcare.3`), you can use one of the following methods:
+
+* **Option 1: TuxCare Patcher (Automated). Recommended for projects with multiple TuxCare dependencies.**
+
+  The TuxCare Patcher automatically detects all TuxCare dependencies in your `package.json` and updates them to the latest available versions.
+
+  <CodeWithCopy>
+
+  ```text
+  tuxcare-patch-js --upgrade
+  ```
+
+  </CodeWithCopy>
+
+* **Option 2: Manual Update via CLI (Single Dependency)**
+
+  If you want to update a single TuxCare dependency, use the npm install command with the specific version. This automatically updates both `package.json` and `package-lock.json`:
+
+  <CodeWithCopy>
+
+  ```text
+  npm install requirejs@npm:@els-js/[email protected]
+  ```
+
+  </CodeWithCopy>
+
+* **Option 3: Manual Update via package.json (Multiple Dependencies)**
+
+  If you want to update several TuxCare dependencies, manually update the version strings in your `package.json`, then remove installed files and clear npm cache to avoid conflicts:
+
+  <CodeWithCopy>
+
+  ```text
+  rm -rf node_modules package-lock.json && npm cache clean --force
+  npm install
+  ```
+
+  </CodeWithCopy>
+
+## Resolved CVEs
+
+Fixes for the following vulnerabilities are available in ELS for RequireJS from TuxCare versions:
+
+| CVE ID         | CVE Type | Severity | Affected Libraries | Vulnerable Versions |
+| :------------: | :------: |:--------:|:------------------:| :----------------: |
+| CVE-2024-38999 | Direct   | Critical | requirejs          | -                  |
+
+If you are interested in the TuxCare Endless Lifecycle Support, contact [[email protected]](mailto:[email protected]).
+
+