fix(form-wdith): Update style.css

[jackseceng]

Update form width on main page to 400px

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ code/snyk check is complete. No issues have been found. (View Details)

[github-actions]

🔍 Vulnerabilities of jackseceng/linkshort:334

📦 Image Reference jackseceng/linkshort:334

digest	sha256:bf4338e236e538be90243ecbd4e2bc1d4a2a54f0432351b7dfaa6b5113ee049b
vulnerabilities
platform	linux/amd64
size	41 MB
packages	33

pip 25.2 (pypi) pkg:pypi/[email protected] Improper Link Resolution Before File Access ('Link Following') Affected range <=25.2 Fixed version Not Fixed CVSS Score 5.9 CVSS Vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N EPSS Score 0.055% EPSS Percentile 17th percentile Description Summary In the fallback extraction path for source distributions, pip used Python’s tarfile module without verifying that symbolic/hard link targets resolve inside the intended extraction directory. A malicious sdist can include links that escape the target directory and overwrite arbitrary files on the invoking host during pip install. Impact Successful exploitation enables arbitrary file overwrite outside the build/extraction directory on the machine running pip. This can be leveraged to tamper with configuration or startup files and may lead to further code execution depending on the environment, but the direct, guaranteed impact is integrity compromise on the vulnerable system. Conditions The issue is triggered when installing an attacker-controlled sdist (e.g., from an index or URL) and the fallback extraction code path is used. No special privileges are required beyond running pip install; active user action is necessary. Remediation The fix, while available as a patch that can be manually applied, has not yet been put into a numbered version but is planned for 25.3. Using a Python interpreter that implements the safe-extraction behavior described by PEP 706 provides additional defense in depth for other tarfile issues but is not a substitute for upgrading pip for this specific flaw.