t3x-rte_ckeditor_image

Projects that follow the best practices below can voluntarily self-certify and show that they've achieved an Open Source Security Foundation (OpenSSF) best practices badge.

There is no set of practices that can guarantee that software will never have defects or vulnerabilities; even formal methods can fail if the specifications or assumptions are wrong. Nor is there any set of practices that can guarantee that a project will sustain a healthy and well-functioning development community. However, following best practices can help improve the results of projects. For example, some practices enable multi-person review before release, which can both help find otherwise hard-to-find technical vulnerabilities and help build trust and a desire for repeated interaction among developers from different companies. To earn a badge, all MUST and MUST NOT criteria must be met, all SHOULD criteria must be met OR be unmet with justification, and all SUGGESTED criteria must be met OR unmet (we want them considered at least). If you want to enter justification text as a generic comment, instead of being a rationale that the situation is acceptable, start the text block with '//' followed by a space. Feedback is welcome via the GitHub site as issues or pull requests There is also a mailing list for general discussion.

We gladly provide the information in several locales, however, if there is any conflict or inconsistency between the translations, the English version is the authoritative version.
If this is your project, please show your baseline badge status on your project page! The baseline badge status looks like this: Baseline badge level for project 11718 is baseline-2 Here is how to embed the baseline badge:
You can show your baseline badge status by embedding this in your markdown file:
[![OpenSSF Baseline](https://www.bestpractices.dev/projects/11718/baseline)](https://www.bestpractices.dev/projects/11718)
or by embedding this in your HTML:
<a href="https://www.bestpractices.dev/projects/11718"><img src="https://www.bestpractices.dev/projects/11718/baseline"></a>


These are the Baseline Level 1 criteria. These are criteria version v2025.10.10.

Baseline Series: Baseline Level 1 Baseline Level 2 Baseline Level 3

        

 Basics

  • General

    Note that other projects may use the same name.

    Image support in CKEditor for the TYPO3 ecosystem

    Please use SPDX license expression format; examples include "Apache-2.0", "BSD-2-Clause", "BSD-3-Clause", "GPL-2.0+", "LGPL-3.0+", "MIT", and "(BSD-2-Clause OR Ruby)". Do not include single quotes or double quotes.
    If there is more than one language, list them as comma-separated values (spaces optional) and sort them from most to least used. If there is a long list, please list at least the first three most common ones. If there is no language (e.g., this is a documentation-only or test-only project), use the single character "-". Please use a conventional capitalization for each language, e.g., "JavaScript".
    The Common Platform Enumeration (CPE) is a structured naming scheme for information technology systems, software, and packages. It is used in a number of systems and databases when reporting vulnerabilities.

 Controls 24/24 ●

  • Controls


    Enough for a badge!

    When a user attempts to read or modify a sensitive resource in the project's authoritative repository, the system MUST require the user to complete a multi-factor authentication process. [OSPS-AC-01.01]
    Enforce multi-factor authentication for the project's version control system, requiring collaborators to provide a second form of authentication when accessing sensitive data or modifying repository settings. Passkeys are acceptable for this control.

    GitHub organization (netresearch) supports multi-factor authentication for all members accessing repository settings, secrets, and deployment configurations.


    Enough for a badge!

    When a new collaborator is added, the version control system MUST require manual permission assignment, or restrict the collaborator permissions to the lowest available privileges by default. [OSPS-AC-02.01]
    Most public version control systems are configured in this manner. Ensure the project's version control system always assigns the lowest available permissions to collaborators by default when added, granting additional permissions only when necessary.

    GitHub organization manages collaborator access via teams (@netresearch/typo3, @netresearch/sec). New collaborators receive read access by default and must be explicitly added to teams for write access.


    Enough for a badge!

    When a direct commit is attempted on the project's primary branch, an enforcement mechanism MUST prevent the change from being applied. [OSPS-AC-03.01]
    If the VCS is centralized, set branch protection on the primary branch in the project's VCS. Alternatively, use a decentralized approach, like the Linux kernel's, where changes are first proposed in another repository, and merging changes into the primary repository requires a specific separate act.

    Branch protection rules on main branch prevent direct commits. All changes require pull requests with status checks passing: https://github.com/netresearch/t3x-rte_ckeditor_image/settings/branches


    Enough for a badge!

    When an attempt is made to delete the project's primary branch, the version control system MUST treat this as a sensitive activity and require explicit confirmation of intent. [OSPS-AC-03.02]
    Set branch protection on the primary branch in the project's version control system to prevent deletion.

    GitHub branch protection prevents deletion of the main branch. Branch deletion requires explicit admin override.


    Enough for a badge!

    When a CI/CD pipeline accepts an input parameter, that parameter MUST be sanitized and validated prior to use in the pipeline. [OSPS-BR-01.01]

    GitHub Actions workflows use proper input handling. Workflow inputs are typed and validated. No direct interpolation of github.event.* in run: blocks. Step-security/harden-runner monitors CI execution.


    Enough for a badge!

    When a CI/CD pipeline uses a branch name in its functionality, that name value MUST be sanitized and validated prior to use in the pipeline. [OSPS-BR-01.02]

    Branch names in CI/CD are handled safely through GitHub Actions context variables with proper quoting. No direct shell interpolation of branch names in run: blocks.


    Enough for a badge!

    When the project lists a URI as an official project channel, that URI MUST be exclusively delivered using encrypted channels. [OSPS-BR-03.01]
    Configure the project's websites and version control systems to use encrypted channels such as SSH or HTTPS for data transmission. Ensure all tools and domains referenced in project documentation can only be accessed via encrypted channels.

    All official project channels use encrypted transmission: GitHub (HTTPS), Packagist (HTTPS), docs.typo3.org (HTTPS), TYPO3 TER (HTTPS).


    Enough for a badge!

    When the project lists a URI as an official distribution channel, that URI MUST be exclusively delivered using encrypted channels. [OSPS-BR-03.02]
    Configure the project's release pipeline to only fetch data from websites, API responses, and other services which use encrypted channels such as SSH or HTTPS for data transmission.

    Distribution exclusively via encrypted channels: Composer/Packagist (HTTPS), GitHub Releases (HTTPS), TYPO3 TER (HTTPS). SLSA Level 3 provenance provides additional integrity verification.


    Enough for a badge!

    The project MUST prevent the unintentional storage of unencrypted sensitive data, such as secrets and credentials, in the version control system. [OSPS-BR-07.01]
    Configure .gitignore or equivalent to exclude files that may contain sensitive information. Use pre-commit hooks and automated scanning tools to detect and prevent the inclusion of sensitive data in commits.

    Secrets managed via GitHub Secrets (CODECOV_TOKEN, TYPO3_TER_ACCESS_TOKEN). .gitignore excludes sensitive files. No credentials stored in version control. Repository scanned for leaked credentials.


    Enough for a badge!

    When the project has made a release, the project documentation MUST include user guides for all basic functionality. [OSPS-DO-01.01]
    Create user guides or documentation for all basic functionality of the project, explaining how to install, configure, and use the project's features. If there are any known dangerous or destructive actions available, include highly-visible warnings.

    User documentation at https://docs.typo3.org/p/netresearch/rte-ckeditor-image/main/en-us/ and README.md with installation, configuration, and usage instructions.


    Enough for a badge!

    When the project has made a release, the project documentation MUST include a guide for reporting defects. [OSPS-DO-02.01]
    It is recommended that projects use their VCS default issue tracker. If an external source is used, ensure that the project documentation and contributing guide clearly and visibly explain how to use the reporting system. It is recommended that project documentation also sets expectations for how defects will be triaged and resolved.

    Defect reporting guide in CONTRIBUTING.md: check existing issues, review README, create issue with bug report template. Issue templates at .github/ISSUE_TEMPLATE/: https://github.com/netresearch/t3x-rte_ckeditor_image/blob/main/CONTRIBUTING.md


    Enough for a badge!

    While active, the project MUST have one or more mechanisms for public discussions about proposed changes and usage obstacles. [OSPS-GV-02.01]
    Establish one or more mechanisms for public discussions within the project, such as mailing lists, instant messaging, or issue trackers, to facilitate open communication and feedback.

    Public discussion via GitHub Issues and Pull Requests. All proposed changes discussed in PR reviews. Feature requests accepted via issue tracker: https://github.com/netresearch/t3x-rte_ckeditor_image/issues


    Enough for a badge!

    While active, the project documentation MUST include an explanation of the contribution process. [OSPS-GV-03.01]
    Create a CONTRIBUTING.md or CONTRIBUTING/ directory to outline the contribution process including the steps for submitting changes, and engaging with the project maintainers.

    Contribution process documented in CONTRIBUTING.md with requirements for issue creation, PR submission, test plans, and code formatting: https://github.com/netresearch/t3x-rte_ckeditor_image/blob/main/CONTRIBUTING.md


    Enough for a badge!

    While active, the license for the source code MUST meet the OSI Open Source Definition or the FSF Free Software Definition. [OSPS-LE-02.01]
    Add a LICENSE file to the project's repo with a license that is an approved license by the Open Source Initiative (OSI), or a free license as approved by the Free Software Foundation (FSF). Examples of such licenses include the MIT, BSD 2-clause, BSD 3-clause revised, Apache 2.0, Lesser GNU General Public License (LGPL), and the GNU General Public License (GPL). Releasing to the public domain meets this control if there are no other encumbrances such as patents.

    Source code licensed under AGPL-3.0-or-later, which is both OSI-approved and FSF-approved. License declared in composer.json and LICENSE file.


    Enough for a badge!

    While active, the license for the released software assets MUST meet the OSI Open Source Definition or the FSF Free Software Definition. [OSPS-LE-02.02]
    If a different license is included with released software assets, ensure it is an approved license by the Open Source Initiative (OSI), or a free license as approved by the Free Software Foundation (FSF). Examples of such licenses include the MIT, BSD 2-clause, BSD 3-clause revised, Apache 2.0, Lesser GNU General Public License (LGPL), and the GNU General Public License (GPL). Note that the license for the released software assets may be different than the source code.

    Released software licensed under AGPL-3.0-or-later (OSI and FSF approved). License included in Composer package distribution.


    Enough for a badge!

    While active, the license for the source code MUST be maintained in the corresponding repository's LICENSE file, COPYING file, or LICENSE/ directory. [OSPS-LE-03.01]
    Include the project's source code license in the project's LICENSE file, COPYING file, or LICENSE/ directory to provide visibility and clarity on the licensing terms. The filename MAY have an extension. If the project has multiple repositories, ensure that each repository includes the license file.

    LICENSE file in repository root contains full AGPL-3.0-or-later license text: https://github.com/netresearch/t3x-rte_ckeditor_image/blob/main/LICENSE


    Enough for a badge!

    While active, the license for the released software assets MUST be included in the released source code, or in a LICENSE file, COPYING file, or LICENSE/ directory alongside the corresponding release assets. [OSPS-LE-03.02]
    Include the project's released software assets license in the released source code, or in a LICENSE file, COPYING file, or LICENSE/ directory alongside the corresponding release assets to provide visibility and clarity on the licensing terms. The filename MAY have an extension. If the project has multiple repositories, ensure that each repository includes the license file.

    LICENSE file included in Composer package. composer.json declares license field. All released assets include license reference.


    Enough for a badge!

    While active, the project's source code repository MUST be publicly readable at a static URL. [OSPS-QA-01.01]
    Use a common VCS such as GitHub, GitLab, or Bitbucket. Ensure the repository is publicly readable. Avoid duplication or mirroring of repositories unless highly visible documentation clarifies the primary source. Avoid frequent changes to the repository that would impact the repository URL. Ensure the repository is public.

    Source repository publicly readable at static URL: https://github.com/netresearch/t3x-rte_ckeditor_image


    Enough for a badge!

    The version control system MUST contain a publicly readable record of all changes made, who made the changes, and when the changes were made. [OSPS-QA-01.02]
    Use a common VCS such as GitHub, GitLab, or Bitbucket to maintain a publicly readable commit history. Avoid squashing or rewriting commits in a way that would obscure the author of any commits.

    Git version control maintains complete public record of all changes, authors, and dates. Full commit history available: https://github.com/netresearch/t3x-rte_ckeditor_image/commits/main


    Enough for a badge!

    When the package management system supports it, the source code repository MUST contain a dependency list that accounts for the direct language dependencies. [OSPS-QA-02.01]
    This may take the form of a package manager or language dependency file that enumerates all direct dependencies such as package.json, Gemfile, or go.mod.

    Direct dependencies listed in composer.json (PHP, TYPO3 Core packages) and package.json (JavaScript dependencies). All versions specified with semantic constraints.


    Enough for a badge!

    While active, the project documentation MUST contain a list of any codebases that are considered subprojects. [OSPS-QA-04.01]
    Document any additional subproject code repositories produced by the project and compiled into a release. This documentation should include the status and intent of the respective codebase.

    This is a single-project extension without subprojects. All code is in the main repository.


    Enough for a badge!

    While active, the version control system MUST NOT contain generated executable artifacts. [OSPS-QA-05.01]
    Remove generated executable artifacts in the project's version control system. It is recommended that any scenario where a generated executable artifact appears critical to a process such as testing, it should be instead be generated at build time or stored separately and fetched during a specific well-documented pipeline step.

    No generated executable artifacts in version control. PHP source distributed as-is. JavaScript built from TypeScript sources but no compiled binaries committed.


    Enough for a badge!

    While active, the version control system MUST NOT contain unreviewable binary artifacts. [OSPS-QA-05.02]
    Do not add any unreviewable binary artifacts to the project's version control system. This includes executable application binaries, library files, and similar artifacts. It does not include assets such as graphical images, sound or music files, and similar content typically stored in a binary format.

    No unreviewable binary artifacts in version control. Repository contains only source code, documentation, configuration files, and test fixtures (text-based).


    Enough for a badge!

    While active, the project documentation MUST contain security contacts. [OSPS-VM-02.01]
    Create a security.md (or similarly-named) file that contains security contacts for the project.

    Security contacts documented in SECURITY.md: private reporting via GitHub Security Advisories, email contact typo3@netresearch.de, 48-hour acknowledgment SLA: https://github.com/netresearch/t3x-rte_ckeditor_image/blob/main/SECURITY.md



This data is available under the Community Data License Agreement – Permissive, Version 2.0 (CDLA-Permissive-2.0). This means that a Data Recipient may share the Data, with or without modifications, so long as the Data Recipient makes available the text of this agreement with the shared Data. Please credit Sebastian Mendel and the OpenSSF Best Practices badge contributors.

Project badge entry owned by: Sebastian Mendel.
Entry created on 2026-01-09 06:04:47 UTC, last updated on 2026-02-25 23:29:35 UTC. Last lost passing badge on 2026-02-18 18:05:31 UTC. Last achieved passing badge on 2026-02-18 18:16:24 UTC.