tea/Documentation/Security.rst

.. include:: /Includes.rst.txt

.. _security:

========
Security
========

Libraries and extensions do not need the security check as they should not have
any restrictions concerning the other libraries they are installed alongside
with (unless those would create breakage). Libraries and extension also should
not have a version-controlled `composer.lock` (which usually is used for
security checks).

Instead, the projects and distributions (i.e., for TYPO3 installations) need to
have the security checks.
[TASK] Update docs (#404) See https://github.com/TYPO3-Documentation/TYPO3CMS-Guide-HowToDocument/commit/c2bb63beadb7cc1ea6eb3496613c3376f970d4c9 for further details. The README.md should mostly only cover the abstract and links. The composer commands are the core value of this extension. List all commands in the documentation and copy the descriptions from the `composer.json`. This lets the global search at docs.typo3.org find these commands. Remove superfluous Linters page, which is integrated now in the Running page. Use sentence case in page titles in order to conform to the TYPO3 documentation standards. The ambiguous :ts: text role has been removed to not confuse the writer with typescript and typoscript. Add the common extension destinations to `composer.json`. (Packagist displays them in a prominent place.) 2022-04-12 19:00:11 +02:00			`.. include:: /Includes.rst.txt`

			`.. _security:`

			`========`
			`Security`
			`========`

			`Libraries and extensions do not need the security check as they should not have`
			`any restrictions concerning the other libraries they are installed alongside`
			`with (unless those would create breakage). Libraries and extension also should`
			not have a version-controlled `composer.lock` (which usually is used for
			`security checks).`

			`Instead, the projects and distributions (i.e., for TYPO3 installations) need to`
			`have the security checks.`