Skip to content

Commit 9f9a616

Browse files
sboldyrevasboldyreva
authored
Merge pull request #526 from sboldyreva/claude/format-els-pages-VwAxe
ELS for Libraries: PHP format updates
2 parents b9c6440 + 7d56e00 commit 9f9a616

23 files changed

Lines changed: 1198 additions & 1150 deletions

File tree

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -486,6 +486,12 @@ export default {
486486
path: '/els-for-libraries/dotnet/',
487487
icon: '/images/dotnet-logo.webp',
488488
},
489+
{
490+
title: 'Resources',
491+
type: 'section-header',
492+
icon: '/images/star.webp',
493+
},
494+
"/els-for-libraries/managing-els-repository/",
489495
]
490496
},
491497
],

‎docs/.vuepress/public/images/star.webp‎

296 Bytes
Loading

‎docs/els-for-libraries/aws-sdk-php/README.md‎

Lines changed: 54 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -8,66 +8,77 @@ Endless Lifecycle Support (ELS) for AWS SDK for PHP from TuxCare provides securi
88

99
Other versions upon request.
1010

11-
## Connection to ELS for AWS SDK for PHP Repository
11+
## Installation
1212

13-
This guide outlines the steps needed to integrate the TuxCare ELS for AWS SDK for PHP repository into your application. The repository provides trusted AWS SDK for PHP library versions that can be easily integrated into your **Composer** projects.
13+
<ELSPrerequisites>
1414

15-
### Step 1: Get user credentials
15+
* Nexus repository access credentials (username and password) — contact [[email protected]](mailto:[email protected])
16+
* To browse available artifacts, visit TuxCare [Nexus](https://nexus.repo.tuxcare.com/#browse/browse:els_php) and click Sign in in the top right corner. You may need to refresh the page after logging in.
1617

17-
You need a username and password in order to use the TuxCare ELS for AWS SDK for PHP repository. Anonymous access is disabled. To receive the credentials, please contact [[email protected]](mailto:[email protected]).
18+
</ELSPrerequisites>
1819

19-
### Step 2: Configure Composer authentication
20+
<ELSSteps>
2021

21-
1. Create or edit the `auth.json` file for the user running Composer:
22+
1. Locate the `auth.json` file
2223

23-
* **Linux/macOS**:
24+
Composer reads credentials from a per-user `auth.json`. Create or edit the file at:
2425

25-
```text
26-
~/.composer/auth.json
27-
```
26+
* **Linux/macOS**:
27+
28+
```
29+
~/.composer/auth.json
30+
```
2831
29-
* **Windows**:
32+
* **Windows**:
33+
34+
```
35+
%APPDATA%\Composer\auth.json
36+
```
3037
31-
```text
32-
%APPDATA%\Composer\auth.json
33-
```
38+
2. Add your TuxCare credentials
3439
35-
2. Use either the Composer CLI or edit `auth.json` directly to add your credentials for `nexus.repo.tuxcare.com`.
40+
Use either the Composer CLI or edit `auth.json` directly to add credentials for `nexus.repo.tuxcare.com`:
3641
3742
<CodeTabs :tabs="[
3843
{ title: 'Composer CLI', content: `composer config --global --auth http-basic.nexus.repo.tuxcare.com USERNAME PASSWORD` },
3944
{ title: 'auth.json', content: authjson }
4045
]" />
4146
42-
Replace `USERNAME` and `PASSWORD` with the credentials you received in [Step 1](#step-1-get-user-credentials).
47+
Replace `USERNAME` and `PASSWORD` with the credentials provided by TuxCare.
4348
44-
### Step 3: Register the TuxCare repository
49+
3. Register the TuxCare repository
4550
46-
Add the `els_php` Composer repository either via CLI or by editing `composer.json`:
51+
Add the `els_php` Composer repository either via CLI or by editing `composer.json`:
4752
48-
<CodeTabs :tabs="[
49-
{ title: 'Composer CLI', content: cli },
50-
{ title: 'composer.json', content: composerjson }
51-
]" />
53+
<CodeTabs :tabs="[
54+
{ title: 'Composer CLI', content: cli },
55+
{ title: 'composer.json', content: composerjson }
56+
]" />
5257
53-
### Step 4: Install AWS SDK for PHP
58+
4. Install AWS SDK for PHP
5459
55-
Install the TuxCare-maintained AWS SDK for PHP release that matches your project:
60+
Install the TuxCare-maintained AWS SDK for PHP release that matches your project:
5661
57-
<CodeTabs :tabs="[
58-
{ title: 'Composer CLI', content: `composer require aws/aws-sdk-php:3.263.4-p1+tuxcare` },
59-
{ title: 'composer.json', content: pkgjson }
60-
]" />
62+
<CodeTabs :tabs="[
63+
{ title: 'Composer CLI', content: `composer require aws/aws-sdk-php:3.263.4-p1+tuxcare` },
64+
{ title: 'composer.json', content: pkgjson }
65+
]" />
6166
62-
**Check the exact version listed in your TuxCare Nexus account to ensure you receive the most recent patched release.**
67+
**Check the exact version listed in your TuxCare Nexus account to ensure you receive the most recent patched release.**
6368
64-
If you edited `composer.json` manually, run `composer update` to install the package:
69+
:::tip
6570
66-
```text
67-
composer update
68-
```
71+
If you edited `composer.json` manually, run `composer update` to install the package:
72+
73+
```
74+
composer update
75+
```
76+
77+
Composer will resolve dependencies against the TuxCare repository and install the patched releases.
6978
70-
Composer will resolve dependencies against the TuxCare repository and install the patched releases.
79+
:::
80+
81+
</ELSSteps>
7182
7283
### Composer Repository Configuration
7384
@@ -93,26 +104,6 @@ it usually means your project requires a package version that is not yet availab
93104
94105
This allows Composer to fall back to Packagist for packages not available in the TuxCare repository, while still preferring TuxCare patches when available.
95106
96-
## Vulnerability Exploitability eXchange (VEX)
97-
98-
VEX is a machine-readable format that tells you if a known vulnerability is actually exploitable in your product. It reduces false positives and helps prioritize real risks.
99-
100-
TuxCare provides VEX for AWS SDK for PHP ELS versions: [security.tuxcare.com/vex/cyclonedx/els_lang_php/aws-sdk-php/](https://security.tuxcare.com/vex/cyclonedx/els_lang_php/aws-sdk-php/).
101-
102-
## How to Upgrade to a Newer Version
103-
104-
If you have already installed a TuxCare AWS SDK for PHP package and want to upgrade to a newer release, update the version string in your `composer.json` file or run the `composer require` command with the new version:
105-
106-
```text
107-
composer require aws/aws-sdk-php:VERSION-pN+tuxcare
108-
```
109-
110-
Then run `composer update` to apply the changes:
111-
112-
```text
113-
composer update
114-
```
115-
116107
## Resolved CVEs in AWS SDK for PHP
117108
118109
Fixes for the following vulnerabilities are available in ELS for AWS SDK for PHP from TuxCare:
@@ -129,7 +120,15 @@ Fixes for the following vulnerabilities are available in ELS for AWS SDK for PHP
129120
130121
</TableTabs>
131122
132-
If you are interested in the TuxCare Endless Lifecycle Support, contact [[email protected]](mailto:[email protected]).
123+
## What's Next?
124+
125+
<WhatsNext hide-title>
126+
127+
* ![](/images/shield-alert.webp) [VEX feed](https://security.tuxcare.com/vex/cyclonedx/els_lang_php/aws/aws-sdk-php/) — Vulnerability Exploitability eXchange feed
128+
* ![](/images/eye.webp) [CVE Tracker](https://tuxcare.com/cve-tracker/) — Track vulnerability fixes and updates
129+
* ![](/images/wrench.webp) [Managing the ELS repository](/els-for-libraries/managing-els-repository/) — Upgrade to a newer version
130+
131+
</WhatsNext>
133132
134133
<script setup>
135134

‎docs/els-for-libraries/browsershot/README.md‎

Lines changed: 55 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -8,66 +8,77 @@ Endless Lifecycle Support (ELS) for Browsershot from TuxCare provides security f
88

99
Other versions upon request.
1010

11-
## Connection to ELS for Browsershot Repository
11+
## Installation
1212

13-
This guide outlines the steps needed to integrate the TuxCare ELS for Browsershot repository into your application. The repository provides trusted Browsershot packages that can be easily integrated into your **Composer** projects.
13+
<ELSPrerequisites>
1414

15-
### Step 1: Get user credentials
15+
* Nexus repository access credentials (username and password) — contact [[email protected]](mailto:[email protected])
16+
* To browse available artifacts, visit TuxCare [Nexus](https://nexus.repo.tuxcare.com/#browse/browse:els_php) and click Sign in in the top right corner. You may need to refresh the page after logging in.
1617

17-
You need a username and password in order to use TuxCare ELS for Browsershot repository. Anonymous access is disabled. To receive the credentials, please contact [[email protected]](mailto:[email protected]).
18+
</ELSPrerequisites>
1819

19-
### Step 2: Configure Composer authentication
20+
<ELSSteps>
2021

21-
1. Create or edit the `auth.json` file for the user running Composer:
22+
1. Locate the `auth.json` file
2223

23-
* **Linux/macOS**:
24+
Composer reads credentials from a per-user `auth.json`. Create or edit the file at:
2425

25-
```text
26-
~/.composer/auth.json
27-
```
26+
* **Linux/macOS**:
27+
28+
```
29+
~/.composer/auth.json
30+
```
2831
29-
* **Windows**:
32+
* **Windows**:
33+
34+
```
35+
%APPDATA%\Composer\auth.json
36+
```
3037
31-
```text
32-
%APPDATA%\Composer\auth.json
33-
```
38+
2. Add your TuxCare credentials
3439
35-
2. Use either the Composer CLI or edit `auth.json` directly to add your credentials for `nexus.repo.tuxcare.com`.
40+
Use either the Composer CLI or edit `auth.json` directly to add credentials for `nexus.repo.tuxcare.com`:
3641
3742
<CodeTabs :tabs="[
3843
{ title: 'Composer CLI', content: `composer config --global --auth http-basic.nexus.repo.tuxcare.com USERNAME PASSWORD` },
3944
{ title: 'auth.json', content: authjson }
4045
]" />
4146
42-
Replace `USERNAME` and `PASSWORD` with the credentials you received in [Step 1](#step-1-get-user-credentials).
47+
Replace `USERNAME` and `PASSWORD` with the credentials provided by TuxCare.
4348
44-
### Step 3: Register the TuxCare repository
49+
3. Register the TuxCare repository
4550
46-
Add the `els_php` Composer repository either via CLI or by editing `composer.json`:
51+
Add the `els_php` Composer repository either via CLI or by editing `composer.json`:
4752
48-
<CodeTabs :tabs="[
49-
{ title: 'Composer CLI', content: cli },
50-
{ title: 'composer.json', content: composerjson }
51-
]" />
53+
<CodeTabs :tabs="[
54+
{ title: 'Composer CLI', content: cli },
55+
{ title: 'composer.json', content: composerjson }
56+
]" />
5257
53-
### Step 4: Install Browsershot
58+
4. Install Browsershot
5459
55-
Install the TuxCare-maintained Browsershot release that matches your project:
60+
Install the TuxCare-maintained Browsershot release that matches your project:
5661
57-
<CodeTabs :tabs="[
58-
{ title: 'Composer CLI', content: `composer require spatie/browsershot:3.61.0-p1+tuxcare` },
59-
{ title: 'composer.json', content: pkgjson }
60-
]" />
62+
<CodeTabs :tabs="[
63+
{ title: 'Composer CLI', content: `composer require spatie/browsershot:3.61.0-p1+tuxcare` },
64+
{ title: 'composer.json', content: pkgjson }
65+
]" />
6166
62-
**Check the exact version listed in your TuxCare Nexus account to ensure you receive the most recent patched release.**
67+
**Check the exact version listed in your TuxCare Nexus account to ensure you receive the most recent patched release.**
6368
64-
If you edited `composer.json` manually, run `composer update` to install the package:
69+
:::tip
6570
66-
```text
67-
composer update
68-
```
71+
If you edited `composer.json` manually, run `composer update` to install the package:
72+
73+
```
74+
composer update
75+
```
76+
77+
Composer will resolve dependencies against the TuxCare repository and install the patched releases.
6978
70-
Composer will resolve dependencies against the TuxCare repository and install the patched releases.
79+
:::
80+
81+
</ELSSteps>
7182
7283
### Composer Repository Configuration
7384
@@ -93,27 +104,7 @@ it usually means your project requires a package version that is not yet availab
93104
94105
This allows Composer to fall back to Packagist for packages not available in the TuxCare repository, while still preferring TuxCare patches when available.
95106
96-
## Vulnerability Exploitability eXchange (VEX)
97-
98-
VEX is a machine-readable format that tells you if a known vulnerability is actually exploitable in your product. It reduces false positives and helps prioritize real risks.
99-
100-
TuxCare provides VEX for Browsershot ELS versions: [security.tuxcare.com/vex/cyclonedx/els_lang_php/spatie-browsershot/](https://security.tuxcare.com/vex/cyclonedx/els_lang_php/spatie-browsershot/)
101-
102-
## How to Upgrade to a Newer Version
103-
104-
If you have already installed a TuxCare Browsershot package and want to upgrade to a newer release, update the version string in your `composer.json` file or run the `composer require` command with the new version:
105-
106-
```text
107-
composer require spatie/browsershot:VERSION-pN+tuxcare
108-
```
109-
110-
Then run `composer update` to apply the changes:
111-
112-
```text
113-
composer update
114-
```
115-
116-
## Resolved CVEs
107+
## Resolved CVEs in Browsershot
117108
118109
Fixes for the following vulnerabilities are available in ELS for Browsershot from TuxCare:
119110
@@ -142,7 +133,15 @@ Fixes for the following vulnerabilities are available in ELS for Browsershot fro
142133
143134
</TableTabs>
144135
145-
If you are interested in the TuxCare Endless Lifecycle Support, contact [[email protected]](mailto:[email protected]).
136+
## What's Next?
137+
138+
<WhatsNext hide-title>
139+
140+
* ![](/images/shield-alert.webp) [VEX feed](https://security.tuxcare.com/vex/cyclonedx/els_lang_php/spatie/browsershot/) — Vulnerability Exploitability eXchange feed
141+
* ![](/images/eye.webp) [CVE Tracker](https://tuxcare.com/cve-tracker/) — Track vulnerability fixes and updates
142+
* ![](/images/wrench.webp) [Managing the ELS repository](/els-for-libraries/managing-els-repository/) — Upgrade to a newer version
143+
144+
</WhatsNext>
146145
147146
<script setup>
148147
@@ -182,4 +181,3 @@ const pkgjson =
182181
}`
183182
184183
</script>
185-

0 commit comments

Comments
 (0)