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 2 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 18/18 ●

  • Controls


    Enough for a badge!

    When a CI/CD task is executed with no permissions specified, the CI/CD system MUST default the task's permissions to the lowest permissions granted in the pipeline. [OSPS-AC-04.01]
    Configure the project's settings to assign the lowest available permissions to new pipelines by default, granting additional permissions only when necessary for specific tasks.

    GitHub Actions workflows use permissions: {} at workflow level (no default permissions). Each job explicitly declares only the permissions needed (e.g., contents: read, security-events: write). Step-security/harden-runner enforces least-privilege.


    Enough for a badge!

    When an official release is created, that release MUST be assigned a unique version identifier. [OSPS-BR-02.01]
    Assign a unique version identifier to each release produced by the project, following a consistent naming convention or numbering scheme. Examples include SemVer, CalVer, or git commit id.

    Each release assigned a unique semantic version identifier (e.g., v13.5.0, v13.4.2). 61 unique version tags. CHANGELOG.md adheres to Semantic Versioning: https://github.com/netresearch/t3x-rte_ckeditor_image/releases


    Enough for a badge!

    When an official release is created, that release MUST contain a descriptive log of functional and security modifications. [OSPS-BR-04.01]
    Ensure that all releases include a descriptive change log. It is recommended to ensure that the change log is human-readable and includes details beyond commit messages, such as descriptions of the security impact or relevance to different use cases. To ensure machine readability, place the content under a markdown header such as "## Changelog".

    Each release includes descriptive changelog with functional and security modifications. CHANGELOG.md categorized by Added/Changed/Fixed/Security sections. GitHub Releases include release notes: https://github.com/netresearch/t3x-rte_ckeditor_image/blob/main/CHANGELOG.md


    Enough for a badge!

    When a build and release pipeline ingests dependencies, it MUST use standardized tooling where available. [OSPS-BR-05.01]
    Use a common tooling for your ecosystem, such as package managers or dependency management tools to ingest dependencies at build time. This may include using a dependency file, lock file, or manifest to specify the required dependencies, which are then pulled in by the build system.

    Build and release pipeline uses standardized tooling: Composer (PHP standard package manager), npm (JavaScript standard), PHPUnit (standard PHP testing), Playwright (standard E2E testing). All tools are widely-adopted industry standards.


    Enough for a badge!

    When an official release is created, that release MUST be signed or accounted for in a signed manifest including each asset's cryptographic hashes. [OSPS-BR-06.01]
    Sign all released software assets at build time with a cryptographic signature or attestations, such as GPG or PGP signature, Sigstore signatures, SLSA provenance, or SLSA VSAs. Include the cryptographic hashes of each asset in a signed manifest or metadata file.

    Releases include SLSA Level 3 provenance attestation with cryptographic hashes. Git tags are signed. Provenance.json uploaded to each GitHub Release. Attestation verifiable via gh attestation verify: https://github.com/netresearch/t3x-rte_ckeditor_image/releases


    Enough for a badge!

    When the project has made a release, the project documentation MUST include a description of how the project selects, obtains, and tracks its dependencies. [OSPS-DO-06.01]
    It is recommended to publish this information alongside the project's technical & design documentation on a publicly viewable resource such as the source code repository, project website, or other channel.

    Dependencies documented in composer.json with version constraints (selection). Obtained via Packagist/Composer (standard PHP ecosystem). Tracked via Dependabot (.github/dependabot.yml - daily) and Renovate (renovate.json - auto-merge minor/patch).


    Enough for a badge!

    While active, the project documentation MUST include a list of project members with access to sensitive resources. [OSPS-GV-01.01]
    Document project participants and their roles through such artifacts as members.md, governance.md, maintainers.md, or similar file within the source code repository of the project. This may be as simple as including names or account handles in a list of maintainers, or more complex depending on the project's governance.

    Project Access & Roles section in CONTRIBUTING.md documents teams with access to sensitive resources (@netresearch/typo3 write access, @netresearch/sec security access, admin secrets scope): https://github.com/netresearch/t3x-rte_ckeditor_image/blob/main/CONTRIBUTING.md


    Enough for a badge!

    While active, the project documentation MUST include descriptions of the roles and responsibilities for members of the project. [OSPS-GV-01.02]
    Document project participants and their roles through such artifacts as members.md, governance.md, maintainers.md, or similar file within the source code repository of the project.

    Roles and responsibilities documented via CODEOWNERS (.github/CODEOWNERS mapping file paths to responsible teams), AGENTS.md (AI agent roles), and composer.json (maintainer roles). Teams: @netresearch/typo3 (development), @netresearch/sec (security).


    Enough for a badge!

    While active, the project documentation MUST include a guide for code contributors that includes requirements for acceptable contributions. [OSPS-GV-03.02]
    Extend the CONTRIBUTING.md or CONTRIBUTING/ contents in the project documentation to outline the requirements for acceptable contributions, including coding standards, testing requirements, and submission guidelines for code contributors. It is recommended that this guide is the source of truth for both contributors and approvers.

    CONTRIBUTING.md contains comprehensive contributor guide with acceptable contribution requirements: coding standards (PSR-12+), test plan requirement, issue linking, PR template: https://github.com/netresearch/t3x-rte_ckeditor_image/blob/main/CONTRIBUTING.md


    Enough for a badge!

    While active, the version control system MUST require all code contributors to assert that they are legally authorized to make the associated contributions on every commit. [OSPS-LE-01.01]
    Include a DCO in the project's repository, requiring code contributors to assert that they are legally authorized to commit the associated contributions on every commit. Use a status check to ensure the assertion is made. A CLA also satisfies this requirement. Some version control systems, such as GitHub, may include this in the platform terms of service.

    DCO (Developer Certificate of Origin) sign-off required on all commits via GitHub Actions DCO check workflow (.github/workflows/dco.yml). CONTRIBUTING.md documents the git commit -s requirement: https://github.com/netresearch/t3x-rte_ckeditor_image/blob/main/CONTRIBUTING.md


    Enough for a badge!

    When a commit is made to the primary branch, any automated status checks for commits MUST pass or be manually bypassed. [OSPS-QA-03.01]
    Configure the project's version control system to require that all automated status checks pass or require manual acknowledgement before a commit can be merged into the primary branch. It is recommended that any optional status checks are NOT configured as a pass or fail requirement that approvers may be tempted to bypass.

    Branch protection requires status checks to pass before merging to main. CI matrix (PHP 8.2-8.5 x TYPO3 13.4/14.0) must pass. PHPStan, PHP-CS-Fixer, and CodeQL checks are required.


    Enough for a badge!

    Prior to a commit being accepted, the project's CI/CD pipelines MUST run at least one automated test suite to ensure the changes meet expectations. [OSPS-QA-06.01]
    Automated tests should be run prior to every merge into the primary branch. The test suite should be run in a CI/CD pipeline and the results should be visible to all contributors. The test suite should be run in a consistent environment and should be run in a way that allows contributors to run the tests locally. Examples of test suites include unit tests, integration tests, and end-to-end tests.

    CI pipeline runs automated test suites on every PR: PHPUnit unit tests, PHPUnit functional tests, Playwright E2E tests (11 shards), PHPStan static analysis, PHP-CS-Fixer code style checks: https://github.com/netresearch/t3x-rte_ckeditor_image/actions


    Enough for a badge!

    When the project has made a release, the project documentation MUST include design documentation demonstrating all actions and actors within the system. [OSPS-SA-01.01]
    Include designs in the project documentation that explains the actions and actors. Actors include any subsystem or entity that can influence another segment in the system. Ensure this is updated for new features or breaking changes.

    Architecture Decision Records in Documentation/Architecture/ (e.g., ADR-003-Security-Responsibility-Boundaries.rst documenting system actors and security boundaries). AGENTS.md documents system actors and their interactions.


    Enough for a badge!

    When the project has made a release, the project documentation MUST include descriptions of all external software interfaces of the released software assets. [OSPS-SA-02.01]
    Document all software interfaces (APIs) of the released software assets, explaining how users can interact with the software and what data is expected or produced. Ensure this is updated for new features or breaking changes.

    External software interfaces documented at https://docs.typo3.org/p/netresearch/rte-ckeditor-image/main/en-us/ — includes TypoScript configuration, CKEditor plugin API, TYPO3 Site Set configuration, and extension settings.


    Enough for a badge!

    When the project has made a release, the project MUST perform a security assessment to understand the most likely and impactful potential security problems that could occur within the software. [OSPS-SA-03.01]
    Performing a security assessment informs both project members as well as downstream consumers that the project understands what problems could arise within the software. Understanding what threats could be realized helps the project manage and address risk. This information is useful to downstream consumers to demonstrate the security acumen and practices of the project. Ensure this is updated for new features or breaking changes.

    Automated security assessment via CodeQL (JavaScript vulnerability scanning) and PHPStan level 10 (PHP type-safety analysis) run on every push and PR. Security measures documented in SECURITY.md and ADR-003.


    Enough for a badge!

    While active, the project documentation MUST include a policy for coordinated vulnerability disclosure (CVD), with a clear timeframe for response. [OSPS-VM-01.01]
    Create a SECURITY.md file at the root of the directory, outlining the project's policy for coordinated vulnerability disclosure. Include a method for reporting vulnerabilities. Set expectations for how the project will respond and address reported issues.

    SECURITY.md documents coordinated vulnerability disclosure policy: 48-hour acknowledgment SLA, 7-day fix for critical vulnerabilities, CVE assignment process: https://github.com/netresearch/t3x-rte_ckeditor_image/blob/main/SECURITY.md


    Enough for a badge!

    While active, the project documentation MUST provide a means for private vulnerability reporting directly to the security contacts within the project. [OSPS-VM-03.01]
    Provide a means for security researchers to report vulnerabilities privately to the project. This may be a dedicated email address, a web form, VCS specialized tools, email addresses for security contacts, or other methods.

    Private vulnerability reporting via GitHub Security Advisories: https://github.com/netresearch/t3x-rte_ckeditor_image/security/advisories/new — documented in SECURITY.md.


    Enough for a badge!

    While active, the project documentation MUST publicly publish data about discovered vulnerabilities. [OSPS-VM-04.01]
    Provide information about known vulnerabilities in a predictable public channel, such as a CVE entry, blog post, or other medium. To the degree possible, this information should include affected version(s), how a consumer can determine if they are vulnerable, and instructions for mitigation or remediation.

    Vulnerability data published via GitHub Security Advisories, CHANGELOG.md Security section (e.g., v13.4.0 SVG data URI sanitization), and CVE identifiers assigned per coordinated disclosure process documented in 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.