status-page

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 badge status on your project page! The badge status looks like this: Badge level for project 15113 is passing Here is how to embed it:
You can show your badge status by embedding this in your markdown file:
[![OpenSSF Best Practices](https://www.bestpractices.dev/projects/15113/badge)](https://www.bestpractices.dev/projects/15113)
or by embedding this in your HTML:
<a href="https://www.bestpractices.dev/projects/15113"><img src="https://www.bestpractices.dev/projects/15113/badge"></a>


These are the Passing level criteria. You can also view the Silver or Gold level criteria.

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

        

 Basics 13/13 ●

  • General

    Note that other projects may use the same name.

    Centralized live status board for GCP, AWS, Steam, CS2 Europe, Epic/Fortnite, Spotify, Apple, Android, Grok, ChatGPT, and Claude.

    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.

    Status is a small, self-hosted status board (https://status.szolotov.com) that reads the official public status feeds of 14 vendors (cloud, gaming, platforms, AI and release trackers) and shows them on one page, with a JSON API, an Atom feed, Prometheus metrics and badges. It is built with TanStack Start and React and runs on Cloudflare Workers.

    The project is maintained by one person. Changes go through pull requests into dev, are promoted to a stage preview (https://stage.status.szolotov.com) and then to main, which is released and deployed automatically. CI runs lint, typecheck, unit tests with coverage gates, browser tests with axe accessibility checks in Chromium and WebKit (desktop, iPhone and iPad), CodeQL, OpenSSF Scorecard, dependency review, Trivy, actionlint and zizmor. Dependencies and GitHub Actions are pinned by hash. Security issues are reported privately as described in SECURITY.md.

  • Basic project website content


    Enough for a badge!

    The project website MUST succinctly describe what the software does (what problem does it solve?). [description_good]
    This MUST be in language that potential users can understand (e.g., it uses minimal jargon).

    The README opens with what the software does and the problem it solves: "Official sources. One board. Live status for the cloud, gaming, platform and AI services people actually wait on, read straight from each vendor and never from rumor." The "What it watches" and "How it decides" sections list each service, its official source and how its state is mapped. https://github.com/greenblacked/status-page#readme


    Enough for a badge!

    The project website MUST provide information on how to: obtain, provide feedback (as bug reports or enhancements), and contribute to the software. [interact]

    Obtain: the README "Quick start" (git clone, npm ci, npm run dev, or docker compose) and "Deploy your own" sections, plus tagged GitHub Releases: https://github.com/greenblacked/status-page#quick-start and https://github.com/greenblacked/status-page/releases
    Feedback: GitHub Issues, with a form for requesting a new service: https://github.com/greenblacked/status-page/issues (security issues are reported privately, per SECURITY.md).
    Contribute: CONTRIBUTING.md covers the setup, the branch flow, commit conventions, checks and review: https://github.com/greenblacked/status-page/blob/main/CONTRIBUTING.md


    Enough for a badge!

    The information on how to contribute MUST explain the contribution process (e.g., are pull requests used?) (URL required) [contribution]
    We presume that projects on GitHub use issues and pull requests unless otherwise noted. This information can be short, e.g., stating that the project uses pull requests, an issue tracker, or posts to a mailing list (which one?)

    Non-trivial contribution file in repository: https://github.com/greenblacked/status-page/blob/main/CONTRIBUTING.md.


    Enough for a badge!

    The information on how to contribute SHOULD include the requirements for acceptable contributions (e.g., a reference to any required coding standard). (URL required) [contribution_requirements]

    CONTRIBUTING.md sets out what a contribution must meet:


  • FLOSS license


    Enough for a badge!

    The software produced by the project MUST be released as FLOSS. [floss_license]
    FLOSS is software released in a way that meets the Open Source Definition or Free Software Definition. Examples of such licenses include the CC0, MIT, BSD 2-clause, BSD 3-clause revised, Apache 2.0, Lesser GNU General Public License (LGPL), and the GNU General Public License (GPL). For our purposes, this means that the license MUST be: The software MAY also be licensed other ways (e.g., "GPLv2 or proprietary" is acceptable).

    The MIT license is approved by the Open Source Initiative (OSI).


    Enough for a badge!

    It is SUGGESTED that any required license(s) for the software produced by the project be approved by the Open Source Initiative (OSI). [floss_license_osi]
    The OSI uses a rigorous approval process to determine which licenses are OSS.

    The MIT license is approved by the Open Source Initiative (OSI).


    Enough for a badge!

    The project MUST post the license(s) of its results in a standard location in their source repository. (URL required) [license_location]
    One convention is posting the license as a top-level file named LICENSE or COPYING, which MAY be followed by an extension such as ".txt" or ".md". An alternative convention is to have a directory named LICENSES containing license file(s); these files are typically named as their SPDX license identifier followed by an appropriate file extension, as described in the REUSE Specification. Note that this criterion is only a requirement on the source repository. You do NOT need to include the license file when generating something from the source code (such as an executable, package, or container). For example, when generating an R package for the Comprehensive R Archive Network (CRAN), follow standard CRAN practice: if the license is a standard license, use the standard short license specification (to avoid installing yet another copy of the text) and list the LICENSE file in an exclusion file such as .Rbuildignore. Similarly, when creating a Debian package, you may put a link in the copyright file to the license text in /usr/share/common-licenses, and exclude the license file from the created package (e.g., by deleting the file after calling dh_auto_install). We encourage including machine-readable license information in generated formats where practical.

    Non-trivial license location file in repository: https://github.com/greenblacked/status-page/blob/main/LICENSE.


  • Documentation


    Enough for a badge!

    The project MUST provide basic documentation for the software produced by the project. [documentation_basics]
    This documentation must be in some media (such as text or video) that includes: how to install it, how to start it, how to use it (possibly with a tutorial using examples), and how to use it securely (e.g., what to do and what not to do) if that is an appropriate topic for the software. The security documentation need not be long. The project MAY use hypertext links to non-project material as documentation. If the project does not produce software, choose "not applicable" (N/A).

    Some documentation basics file contents found.


    Enough for a badge!

    The project MUST provide reference documentation that describes the external interface (both input and output) of the software produced by the project. [documentation_interface]
    The documentation of an external interface explains to an end-user or developer how to use it. This would include its application program interface (API) if the software has one. If it is a library, document the major classes/types and methods/functions that can be called. If it is a web application, define its URL interface (often its REST interface). If it is a command-line interface, document the parameters and options it supports. In many cases it's best if most of this documentation is automatically generated, so that this documentation stays synchronized with the software as it changes, but this isn't required. The project MAY use hypertext links to non-project material as documentation. Documentation MAY be automatically generated (where practical this is often the best way to do so). Documentation of a REST interface may be generated using Swagger/OpenAPI. Code interface documentation MAY be generated using tools such as JSDoc (JavaScript), ESDoc (JavaScript), pydoc (Python), devtools (R), pkgdown (R), and Doxygen (many). Merely having comments in implementation code is not sufficient to satisfy this criterion; there needs to be an easy way to see the information without reading through all the source code. If the project does not produce software, choose "not applicable" (N/A).

    The README's Integrations section is the reference for every external interface: each endpoint's path, output format and purpose.

    • /api/status.json (JSON: overall health, headline, counts, and each service's health, summary, source and incidents)
    • /api/history.json
    • /feed.xml (Atom)
    • /api/badge/<service> (Shields.io endpoint badge, with the list of valid service ids and the response for an unknown id)
    • /metrics (Prometheus text format)
    • /healthz and /readyz (status codes and the JSON fields, with when each answers 200 or 503)
      https://github.com/greenblacked/status-page#integrations
      Inputs are documented too: the board's URL parameters (/?q=aws&issues=true) and keyboard shortcuts under "On the board" (https://github.com/greenblacked/status-page#on-the-board), and the build and deploy settings (VITE_STATUS_HISTORY, DEPLOY_URL) under "Deploy your own" and in CONTRIBUTING.md.

  • Other


    Enough for a badge!

    The project sites (website, repository, and download URLs) MUST support HTTPS using TLS. [sites_https]
    This requires that the project home page URL and the version control repository URL begin with "https:", not "http:". You can get free certificates from Let's Encrypt. Projects MAY implement this criterion using (for example) GitHub pages, GitLab pages, or SourceForge project pages. If you support HTTP, we urge you to redirect the HTTP traffic to HTTPS.

    Given only https: URLs.


    Enough for a badge!

    The project MUST have one or more mechanisms for discussion (including proposed changes and issues) that are searchable, allow messages and topics to be addressed by URL, enable new people to participate in some of the discussions, and do not require client-side installation of proprietary software. [discussion]
    Examples of acceptable mechanisms include archived mailing list(s), GitHub issue and pull request discussions, Bugzilla, Mantis, and Trac. Asynchronous discussion mechanisms (like IRC) are acceptable if they meet these criteria; make sure there is a URL-addressable archiving mechanism. Proprietary JavaScript, while discouraged, is permitted.

    GitHub supports discussions on issues and pull requests.


    Enough for a badge!

    The project SHOULD provide documentation in English and be able to accept bug reports and comments about code in English. [english]
    English is currently the lingua franca of computer technology; supporting English increases the number of different potential developers and reviewers worldwide. A project can meet this criterion even if its core developers' primary language is not English.

    All documentation (README, CONTRIBUTING.md, SECURITY.md, CHANGELOG.md, code comments) is written in English, and bug reports and comments are accepted in English through GitHub Issues and pull requests. https://github.com/greenblacked/status-page#readme


    Enough for a badge!

    The project MUST be maintained. [maintained]
    As a minimum, the project should attempt to respond to significant problem and vulnerability reports. A project that is actively pursuing a badge is probably maintained. All projects and people have limited resources, and typical projects must reject some proposed changes, so limited resources and proposal rejections do not by themselves indicate an unmaintained project.

    When a project knows that it will no longer be maintained, it should set this criterion to "Unmet" and use the appropriate mechanism(s) to indicate to others that it is not being maintained. For example, use “DEPRECATED” as the first heading of its README, add “DEPRECATED” near the beginning of its home page, add “DEPRECATED” to the beginning of its code repository project description, add a no-maintenance-intended badge in its README and/or home page, mark it as deprecated in any package repositories (e.g., npm deprecate), and/or use the code repository's marking system to archive it (e.g., GitHub's "archive" setting, GitLab’s "archived" marking, Gerrit's "readonly" status, or SourceForge’s "abandoned" project status). Additional discussion can be found here.

    The project is actively maintained. Commits land on the dev, stage and main branches continuously, and every merge runs CI, CodeQL and dependency review. Releases are cut from main and published on GitHub Releases, with a CHANGELOG. Dependabot keeps npm packages and GitHub Actions up to date. OpenSSF Scorecard runs weekly. https://github.com/greenblacked/status-page/commits and https://github.com/greenblacked/status-page/releases


 Change Control 9/9 ●

  • Public version-controlled source repository


    Enough for a badge!

    The project MUST have a version-controlled source repository that is publicly readable and has a URL. [repo_public]
    The URL MAY be the same as the project URL. The project MAY use private (non-public) branches in specific cases while the change is not publicly released (e.g., for fixing a vulnerability before it is revealed to the public).

    Repository on GitHub, which provides public git repositories with URLs.


    Enough for a badge!

    The project's source repository MUST track what changes were made, who made the changes, and when the changes were made. [repo_track]

    Repository on GitHub, which uses git. git can track the changes, who made them, and when they were made.


    Enough for a badge!

    To enable collaborative review, the project's source repository MUST include interim versions for review between releases; it MUST NOT include only final releases. [repo_interim]
    Projects MAY choose to omit specific interim versions from their public source repositories (e.g., ones that fix specific non-public security vulnerabilities, may never be publicly released, or include material that cannot be legally posted and are not in the final release).

    The public GitHub repository holds every interim change, not just releases: work lands on dev through reviewed pull requests, is promoted to stage (a live preview at stage.status.szolotov.com) and then to main, where releases are tagged. Each commit between releases is visible and reviewable. https://github.com/greenblacked/status-page/commits and https://github.com/greenblacked/status-page/pulls?q=is%3Apr


    Enough for a badge!

    It is SUGGESTED that common distributed version control software be used (e.g., git) for the project's source repository. [repo_distributed]
    Git is not specifically required and projects can use centralized version control software (such as subversion) with justification.

    Repository on GitHub, which uses git. git is distributed.


  • Unique version numbering


    Enough for a badge!

    The project results MUST have a unique version identifier for each release intended to be used by users. [version_unique]
    This MAY be met in a variety of ways including a commit IDs (such as git commit id or mercurial changeset id) or a version number (including version numbers that use semantic versioning or date-based schemes like YYYYMMDD).

    Each release has a unique version number (v0.1.0 through v0.5.0 so far). release.yml derives it from the Conventional Commits since the last tag, sets it in package.json, tags it and publishes a GitHub Release. The running Worker reports its version in the X-Worker-Version header. https://github.com/greenblacked/status-page/releases


    Enough for a badge!

    It is SUGGESTED that the Semantic Versioning (SemVer) or Calendar Versioning (CalVer) version numbering format be used for releases. It is SUGGESTED that those who use CalVer include a micro level value. [version_semver]
    Projects should generally prefer whatever format is expected by their users, e.g., because it is the normal format used by their ecosystem. Many ecosystems prefer SemVer, and SemVer is generally preferred for application programmer interfaces (APIs) and software development kits (SDKs). CalVer tends to be used by projects that are large, have an unusually large number of independently-developed dependencies, have a constantly-changing scope, or are time-sensitive. It is SUGGESTED that those who use CalVer include a micro level value, because including a micro level supports simultaneously-maintained branches whenever that becomes necessary. Other version numbering formats may be used as version numbers, including git commit IDs or mercurial changeset IDs, as long as they uniquely identify versions. However, some alternatives (such as git commit IDs) can cause problems as release identifiers, because users may not be able to easily determine if they are up-to-date. The version ID format may be unimportant for identifying software releases if all recipients only run the latest version (e.g., it is the code for a single website or internet service that is constantly updated via continuous delivery).

    Enough for a badge!

    It is SUGGESTED that projects identify each release within their version control system. For example, it is SUGGESTED that those using git identify each release using git tags. [version_tags]

    Every release is identified by a git tag (v0.1.0, v0.1.1, v0.2.0, v0.3.0, v0.4.0, v0.5.0), created by the release workflow on main. https://github.com/greenblacked/status-page/tags


  • Release notes


    Enough for a badge!

    The project MUST provide, in each release, release notes that are a human-readable summary of major changes in that release to help users determine if they should upgrade and what the upgrade impact will be. The release notes MUST NOT be the raw output of a version control log (e.g., the "git log" command results are not release notes). Projects whose results are not intended for reuse in multiple locations (such as the software for a single website or service) AND employ continuous delivery MAY select "N/A". (URL required) [release_notes]
    The release notes MAY be implemented in a variety of ways. Many projects provide them in a file named "NEWS", "CHANGELOG", or "ChangeLog", optionally with extensions such as ".txt", ".md", or ".html". Historically the term "change log" meant a log of every change, but to meet these criteria what is needed is a human-readable summary. The release notes MAY instead be provided by version control system mechanisms such as the GitHub Releases workflow.

    Non-trivial release notes file in repository: https://github.com/greenblacked/status-page/blob/main/CHANGELOG.md.


    Enough for a badge!

    The release notes MUST identify every publicly known run-time vulnerability fixed in this release that already had a CVE assignment or similar when the release was created. This criterion may be marked as not applicable (N/A) if users typically cannot practically update the software themselves (e.g., as is often true for kernel updates). This criterion applies only to the project results, not to its dependencies. If there are no release notes or there have been no publicly known vulnerabilities, choose N/A. [release_notes_vulns]
    This criterion helps users determine if a given update will fix a vulnerability that is publicly known, to help users make an informed decision about updating. If users typically cannot practically update the software themselves on their computers, but must instead depend on one or more intermediaries to perform the update (as is often the case for a kernel and low-level software that is intertwined with a kernel), the project may choose "not applicable" (N/A) instead, since this additional information will not be helpful to those users. Similarly, a project may choose N/A if all recipients only run the latest version (e.g., it is the code for a single website or internet service that is constantly updated via continuous delivery). This criterion only applies to the project results, not its dependencies. Listing the vulnerabilities of all transitive dependencies of a project becomes unwieldy as dependencies increase and vary, and is unnecessary since tools that examine and track dependencies can do this in a more scalable way.

    No publicly known vulnerability (CVE or similar) has ever been reported against this project's own code, so no release has fixed one. Release notes (CHANGELOG.md and GitHub Releases) include a Security section when security-relevant changes ship (for example, the security headers in 0.5.0). Dependency advisories are handled by Dependabot and dependency review.


 Reporting 8/8 ●

  • Bug-reporting process


    Enough for a badge!

    The project MUST provide a process for users to submit bug reports (e.g., using an issue tracker or a mailing list). (URL required) [report_process]

    Non-trivial SECURITY[.md] file found file in repository: https://github.com/greenblacked/status-page/blob/main/SECURITY.md. [osps_do_02_01]


    Enough for a badge!

    The project SHOULD use an issue tracker for tracking individual issues. [report_tracker]

    GitHub Issues is the issue tracker, with forms for a bug, a card showing the wrong status, and a new-service request. https://github.com/greenblacked/status-page/issues


    Enough for a badge!

    The project MUST acknowledge a majority of bug reports submitted in the last 2-12 months (inclusive); the response need not include a fix. [report_responses]

    No bug reports have been submitted yet (the project's first release was on 2026-09-24), so there are none left unacknowledged. Reports are filed through GitHub Issues and answered by the maintainer. https://github.com/greenblacked/status-page/issues?q=is%3Aissue


    Enough for a badge!

    The project SHOULD respond to a majority (>50%) of enhancement requests in the last 2-12 months (inclusive). [enhancement_responses]
    The response MAY be 'no' or a discussion about its merits. The goal is simply that there be some response to some requests, which indicates that the project is still alive. For purposes of this criterion, projects need not count fake requests (e.g., from spammers or automated systems). If a project is no longer making enhancements, please select "unmet" and include the URL that makes this situation clear to users. If a project tends to be overwhelmed by the number of enhancement requests, please select "unmet" and explain.

    No enhancement requests have been submitted yet; new-service requests have their own issue form and are answered in the issue. https://github.com/greenblacked/status-page/issues?q=is%3Aissue


    Enough for a badge!

    The project MUST have a publicly available archive for reports and responses for later searching. (URL required) [report_archive]

    All bug reports, feature requests, and their responses are kept publicly in GitHub Issues, and code review happens publicly in pull requests. Both are permanently archived and searchable (open and closed): https://github.com/greenblacked/status-page/issues?q=is%3Aissue and https://github.com/greenblacked/status-page/pulls?q=is%3Apr


  • Vulnerability report process


    Enough for a badge!

    The project MUST publish the process for reporting vulnerabilities on the project site. (URL required) [vulnerability_report_process]
    Projects hosted on GitHub SHOULD consider enabling privately reporting a security vulnerability. Projects on GitLab SHOULD consider using its ability for privately reporting a vulnerability. Projects MAY identify a mailing address on https://PROJECTSITE/security, often in the form security@example.org. This vulnerability reporting process MAY be the same as its bug reporting process. Vulnerability reports MAY always be public, but many projects have a private vulnerability reporting mechanism.

    The process is published in SECURITY.md, linked from the README's Security section and shown on the repository's Security tab. Vulnerabilities are reported privately through GitHub's "Report a vulnerability" form. The page explains what to include (affected file or route, reproduction steps, impact), what is in and out of scope, the expected acknowledgement time, and that fixes land on main with credit in the advisory. https://github.com/greenblacked/status-page/blob/main/SECURITY.md


    Enough for a badge!

    If private vulnerability reports are supported, the project MUST include how to send the information in a way that is kept private. (URL required) [vulnerability_report_private]
    Examples include a private defect report submitted on the web using HTTPS (TLS) or an email encrypted using OpenPGP. If vulnerability reports are always public (so there are never private vulnerability reports), choose "not applicable" (N/A).

    Private reports are supported through GitHub private vulnerability reporting. SECURITY.md links straight to the form (Security tab → Advisories → Report a vulnerability). A report there is visible only to the reporter and the maintainer, is discussed in a private draft advisory, and becomes public only when the advisory is published after a fix. SECURITY.md asks reporters not to use public issues, pull requests or discussions. https://github.com/greenblacked/status-page/blob/main/SECURITY.md and https://github.com/greenblacked/status-page/security/advisories/new


    Enough for a badge!

    The project's initial response time for any vulnerability report received in the last 6 months MUST be less than or equal to 14 days. [vulnerability_report_response]
    If there have been no vulnerabilities reported in the last 6 months, choose "not applicable" (N/A).

    No vulnerability reports have been received in the last 6 months; the project's first release was on 2026-09-24. SECURITY.md commits to acknowledging a private report within a few days, well inside 14 days. https://github.com/greenblacked/status-page/blob/main/SECURITY.md


 Quality 13/13 ●

  • Working build system


    Enough for a badge!

    If the software produced by the project requires building for use, the project MUST provide a working build system that can automatically rebuild the software from source code. [build]
    A build system determines what actions need to occur to rebuild the software (and in what order), and then performs those steps. For example, it can invoke a compiler to compile the source code. If an executable is created from source code, it must be possible to modify the project's source code and then generate an updated executable with those modifications. If the software produced by the project depends on external libraries, the build system does not need to build those external libraries. If there is no need to build anything to use the software after its source code is modified, select "not applicable" (N/A).

    The board is TypeScript and React compiled by Vite, and the build is fully automated from source: npm ci installs the locked dependencies, npm run build builds the Node server and client, and npm run build:cf builds the Cloudflare Worker (DEPLOY_TARGET=cloudflare). docker compose up preview builds and serves it with no local Node. CI rebuilds on every pull request and push, on the pinned Node and on Node 24, and smoke-tests the built output. https://github.com/greenblacked/status-page#quick-start and https://github.com/greenblacked/status-page/blob/main/package.json


    Enough for a badge!

    It is SUGGESTED that common tools be used for building the software. [build_common_tools]
    For example, Maven, Ant, cmake, the autotools, make, rake (Ruby), or devtools (R).

    The build uses standard, widely used JavaScript tooling: npm (lockfile-pinned install with npm ci), Vite for bundling, the TypeScript compiler for type checking, Vitest and Playwright for tests, and Biome for lint and formatting. Wrangler builds and deploys the Cloudflare Worker, and Docker Compose offers a no-Node alternative. https://github.com/greenblacked/status-page/blob/main/package.json


    Enough for a badge!

    The project SHOULD be buildable using only FLOSS tools. [build_floss_tools]

    Every tool needed to build the software is FLOSS: Node.js (MIT), npm (Artistic-2.0), Vite (MIT), TypeScript (Apache-2.0), React (MIT), TanStack Start (MIT), Tailwind CSS (MIT), and Wrangler for the Cloudflare Worker build (MIT OR Apache-2.0). The Node build (npm ci && npm run build) runs on any Node host with no proprietary tools; only deploying to Cloudflare (a hosting service) uses a Cloudflare account, and that step is optional. https://github.com/greenblacked/status-page/blob/main/package.json


  • Automated test suite


    Enough for a badge!

    The project MUST use at least one automated test suite that is publicly released as FLOSS (this test suite may be maintained as a separate FLOSS project). The project MUST clearly show or document how to run the test suite(s) (e.g., via a continuous integration (CI) script or via documentation in files such as BUILD.md, README.md, or CONTRIBUTING.md). [test]
    The project MAY use multiple automated test suites (e.g., one that runs quickly, vs. another that is more thorough but requires special equipment). There are many test frameworks and test support systems available, including Selenium (web browser automation), Junit (JVM, Java), RUnit (R), testthat (R).

    The project has automated test suites, released as FLOSS (MIT) in the repository:


    Enough for a badge!

    A test suite SHOULD be invocable in a standard way for that language. [test_invocation]
    For example, "make check", "mvn test", or "rake test" (Ruby).

    The tests run with the standard npm commands for a Node.js project: npm test (the Vitest unit suite), npm run test:coverage (the same with coverage gates), npm run test:e2e (the Playwright browser suite), and npm run check (lint, typecheck, unit tests and repository checks in one go). They are defined in package.json and used the same way in CI. https://github.com/greenblacked/status-page/blob/main/package.json


    Enough for a badge!

    It is SUGGESTED that the test suite cover most (or ideally all) the code branches, input fields, and functionality. [test_most]

    The test suites cover most of the code and functionality.

    • Unit tests (Vitest) cover about 68% of lines and 73% of branches, with CI coverage gates (lines 64, statements 63, branches 58, functions 60) so coverage cannot drop.
    • They exercise every vendor collector against real trimmed payloads, including a malformed payload for each that must read as unknown.
    • Browser tests (Playwright, around 670 across desktop, mobile, iPhone and iPad) cover every user-facing input: search, filters, the URL parameters, keyboard shortcuts, Settings, stars and alerts. They also cover the API routes and accessibility (axe WCAG checks and text contrast).
      https://github.com/greenblacked/status-page/blob/main/vitest.config.ts and https://github.com/greenblacked/status-page/tree/main/e2e

    Enough for a badge!

    It is SUGGESTED that the project implement continuous integration (where new or changed code is frequently integrated into a central code repository and automated tests are run on the result). [test_continuous_integration]

    GitHub Actions runs CI on every pull request into dev, stage and main and on every push to those branches: lint, typecheck, unit tests with coverage gates, builds on two Node versions with a smoke test, browser and accessibility tests in Chromium and WebKit, commit and branch checks, and workflow lint. A single required check, "CI OK", passes only when every job does. Changes are merged frequently through small pull requests into dev and promoted to stage and main. CodeQL and dependency review also run on every pull request. https://github.com/greenblacked/status-page/actions/workflows/ci.yml


  • New functionality testing


    Enough for a badge!

    The project MUST have a general policy (formal or not) that as major new functionality is added to the software produced by the project, tests of that functionality should be added to an automated test suite. [test_policy]
    As long as a policy is in place, even by word of mouth, that says developers should add tests to the automated test suite for major new functionality, select "Met."

    New functionality must come with tests. CONTRIBUTING.md sets the rules:


    Enough for a badge!

    The project MUST have evidence that the test_policy for adding tests has been adhered to in the most recent major changes to the software produced by the project. [tests_are_added]
    Major functionality would typically be mentioned in the release notes. Perfection is not required, merely evidence that tests are typically being added in practice to the automated test suite when new major functionality is added to the software produced by the project.

    Recent major changes each added tests in the same pull request:

    • #55, the board redesign: unit tests grew from 739 to 913. It added new unit tests for the verdict sentence, local time, the background setting, the status glyphs and the search dock geometry, and new browser tests for the phone search dock, 44pt touch targets, the uptime strip on rows, blocked notifications and the 404 page.
    • #53, status mapping, feed and alert fixes: added tests for the severity order, AWS regions, Statuspage notices, stable feed ids, alert debouncing and the npm pin scripts, and raised coverage back above the CI gates.
    • Every change is merged only when CI OK passes, including the coverage thresholds, which cannot drop.
      https://github.com/greenblacked/status-page/pull/55 and https://github.com/greenblacked/status-page/pull/53

    Enough for a badge!

    It is SUGGESTED that this policy on adding tests (see test_policy) be documented in the instructions for change proposals. [tests_documented_added]
    However, even an informal rule is acceptable as long as the tests are being added in practice.

    The instructions for change proposals document the testing rules. CONTRIBUTING.md requires npm run check (including the unit tests) to pass before a pull request, sets coverage thresholds that CI enforces and that must be raised when coverage grows, and requires every new service to add collector tests against real and malformed payloads. In practice tests are added with each major change (#53 and #55 each added dozens). https://github.com/greenblacked/status-page/blob/main/CONTRIBUTING.md#ci and https://github.com/greenblacked/status-page/blob/main/CONTRIBUTING.md#adding-a-service


  • Warning flags


    Enough for a badge!

    The project MUST enable one or more compiler warning flags, a "safe" language mode, or use a separate "linter" tool to look for code quality errors or common simple mistakes, if there is at least one FLOSS tool that can implement this criterion in the selected language. [warnings]
    Examples of compiler warning flags include gcc/clang "-Wall". Examples of a "safe" language mode include JavaScript "use strict" and perl5's "use warnings". A separate "linter" tool is simply a tool that examines the source code to look for code quality errors or common simple mistakes. These are typically enabled within the source code or build instructions.

    Two FLOSS tools check the code, and CI enforces both on every pull request:

    • TypeScript runs in strict mode (tsconfig.json: "strict": true, plus noUnusedLocals and noUnusedParameters), and npm run typecheck fails the build on any type error or unused code. TypeScript also emits ES modules, which are always in JavaScript strict mode.
    • Biome (MIT) lints with its recommended rule set plus an extra accessibility rule, formats the code and sorts imports; biome ci fails on any finding.
      CI also runs actionlint and zizmor on the GitHub Actions workflows, shellcheck on the shell scripts, and CodeQL static analysis.
      https://github.com/greenblacked/status-page/blob/main/tsconfig.json and https://github.com/greenblacked/status-page/blob/main/biome.json

    Enough for a badge!

    The project MUST address warnings. [warnings_fixed]
    These are the warnings identified by the implementation of the warnings criterion. The project should fix warnings or mark them in the source code as false positives. Ideally there would be no warnings, but a project MAY accept some warnings (typically less than 1 warning per 100 lines or less than 10 warnings).

    The project has zero outstanding warnings: CI treats every TypeScript error, unused local or parameter, and Biome lint finding as a failure, so nothing merges with a warning. biome ci . and tsc --noEmit both report none on the current code. The few intentional exceptions are marked in the source as false positives with a biome-ignore comment that must state the reason (a CONTRIBUTING.md rule). CodeQL alerts are fixed or dismissed with a reason. https://github.com/greenblacked/status-page/blob/main/CONTRIBUTING.md#code-style


    Enough for a badge!

    It is SUGGESTED that projects be maximally strict with warnings in the software produced by the project, where practical. [warnings_strict]
    Some warnings cannot be effectively enabled on some projects. What is needed is evidence that the project is striving to enable warning flags where it can, so that errors are detected early.

    Warnings are as strict as practical, and every one fails CI rather than being reported and ignored:

    • TypeScript runs in "strict" mode plus noUnusedLocals and noUnusedParameters, and any is banned by project rule.
    • Biome runs its full recommended rule set, with an extra accessibility rule raised to error, in biome ci mode.
    • Beyond the code, CI lints the shell scripts (shellcheck), the GitHub Actions workflows (actionlint and zizmor), and design tokens (scripts/ci/tokens.sh); runs CodeQL; and enforces accessibility (axe WCAG 2.2 AA and a 4.5:1 text contrast check) in the browser tests.
      Exceptions need an inline biome-ignore with a stated reason.
      https://github.com/greenblacked/status-page/blob/main/tsconfig.json and https://github.com/greenblacked/status-page/blob/main/biome.json

 Security 16/16 ●

  • Secure development knowledge


    Enough for a badge!

    The project MUST have at least one primary developer who knows how to design secure software. (See ‘details’ for the exact requirements.) [know_secure_design]
    This requires understanding the following design principles, including the 8 principles from Saltzer and Schroeder:
    • economy of mechanism (keep the design as simple and small as practical, e.g., by adopting sweeping simplifications)
    • fail-safe defaults (access decisions should deny by default, and projects' installation should be secure by default)
    • complete mediation (every access that might be limited must be checked for authority and be non-bypassable)
    • open design (security mechanisms should not depend on attacker ignorance of its design, but instead on more easily protected and changed information like keys and passwords)
    • separation of privilege (ideally, access to important objects should depend on more than one condition, so that defeating one protection system won't enable complete access. E.G., multi-factor authentication, such as requiring both a password and a hardware token, is stronger than single-factor authentication)
    • least privilege (processes should operate with the least privilege necessary)
    • least common mechanism (the design should minimize the mechanisms common to more than one user and depended on by all users, e.g., directories for temporary files)
    • psychological acceptability (the human interface must be designed for ease of use - designing for "least astonishment" can help)
    • limited attack surface (the attack surface - the set of the different points where an attacker can try to enter or extract data - should be limited)
    • input validation with allowlists (inputs should typically be checked to determine if they are valid before they are accepted; this validation should use allowlists (which only accept known-good values), not denylists (which attempt to list known-bad values)).
    A "primary developer" in a project is anyone who is familiar with the project's code base, is comfortable making changes to it, and is acknowledged as such by most other participants in the project. A primary developer would typically make a number of contributions over the past year (via code, documentation, or answering questions). Developers would typically be considered primary developers if they initiated the project (and have not left the project more than three years ago), have the option of receiving information on a private vulnerability reporting channel (if there is one), can accept commits on behalf of the project, or perform final releases of the project software. If there is only one developer, that individual is the primary developer. Many books and courses are available to help you understand how to develop more secure software and discuss design. For example, the Secure Software Development Fundamentals course is a free set of three courses that explain how to develop more secure software (it's free if you audit it; for an extra fee you can earn a certificate to prove you learned the material).

    The primary (sole) developer is a DevOps engineer who works with security and infrastructure day to day, and the project's design applies these principles:

    • Economy of mechanism: one small Worker, read-only, with no database, accounts or user data; every vendor is read through one collector pattern.
    • Fail-safe defaults: an unreadable or malformed vendor payload reads as "No data", never as "up". Strict security headers are on by default: a CSP allowing only the board's own origin, HSTS, nosniff, no framing.
    • Complete mediation: every response passes through the same security-header layer, and the deploy token is reachable only by the deploy, preview and rollback steps.
    • Open design: all code, CI and deploy logic are public; security rests on the Cloudflare token kept in a protected GitHub environment, not on secrecy of design.
    • Separation of privilege: deploys need a protected branch and a separate GitHub environment secret, and main takes changes only by pull request with required checks.
    • Least privilege: workflows default to read-only tokens; the token-holding job installs with --ignore-scripts, verifies npm signatures, and runs no project code; pull requests never see credentials.
    • Least common mechanism: each request is served from per-isolate state, with nothing shared between users and no user-writable storage.
    • Psychological acceptability: plain-language states, keyboard shortcuts, accessibility tests, and settings that respect Reduce Motion and Increase Contrast.
    • Limited attack surface: GET-only public endpoints, no user input beyond search and filter parameters, and no uploads or logins.
    • Input validation with allowlists: vendor payloads are parsed into a fixed set of states; the badge endpoint accepts only known service ids; URL filters accept only known categories.
      https://github.com/greenblacked/status-page/blob/main/SECURITY.md

    Enough for a badge!

    At least one of the project's primary developers MUST know of common kinds of errors that lead to vulnerabilities in this kind of software, as well as at least one method to counter or mitigate each of them. [know_common_errors]
    Examples (depending on the type of software) include SQL injection, OS injection, classic buffer overflow, cross-site scripting, missing authentication, and missing authorization. See the CWE/SANS top 25 or OWASP Top 10 for commonly used lists. Many books and courses are available to help you understand how to develop more secure software and discuss common implementation errors that lead to vulnerabilities. For example, the Secure Software Development Fundamentals course is a free set of three courses that explain how to develop more secure software (it's free if you audit it; for an extra fee you can earn a certificate to prove you learned the material).

    The primary developer knows the common vulnerability classes for a web app and its CI/CD pipeline, and the project counters each:

    • XSS / injection: React escapes all rendered text; vendor payloads are parsed into typed data, never injected as HTML; a strict Content-Security-Policy (own origin only) is sent on every response.
    • Untrusted input: vendor feeds are treated as hostile: parsed with fixed schemas and time limits, and a malformed payload reads as "No data" (tested for every collector). URL parameters and badge ids are checked against allowlists.
    • Clickjacking and transport: frame-ancestors none, HSTS, nosniff, and a strict referrer policy.
    • Missing authentication/authorization: there is no login and no write endpoint, so the public surface is read-only GET.
    • Supply-chain and CI attacks: GitHub Actions and npm are pinned by hash; npm registry signatures are verified; workflows run with read-only tokens; pull request code never runs with secrets; the release job is hardened against cache poisoning and untrusted checkout. zizmor, CodeQL, dependency review, Trivy and OpenSSF Scorecard run in CI.
    • Secret exposure: the only secret (the Cloudflare deploy token) lives in a protected GitHub environment and is visible only to the deploy, preview and rollback steps.
      https://github.com/greenblacked/status-page/blob/main/SECURITY.md

  • Use basic good cryptographic practices

    Note that some software does not need to use cryptographic mechanisms. If your project produces software that (1) includes, activates, or enables encryption functionality, and (2) might be released from the United States (US) to outside the US or to a non-US-citizen, you may be legally required to take a few extra steps. Typically this just involves sending an email. For more information, see the encryption section of Understanding Open Source Technology & US Export Controls.

    Enough for a badge!

    The software produced by the project MUST use, by default, only cryptographic protocols and algorithms that are publicly published and reviewed by experts (if cryptographic protocols and algorithms are used). [crypto_published]
    These cryptographic criteria do not always apply because some software has no need to directly use cryptographic capabilities.

    The software implements and configures no cryptography of its own: no hashing, signing, encryption or key handling. Its only use of cryptography is HTTPS, which the hosting platform provides (Cloudflare terminates TLS for the site, and the runtime's standard fetch makes TLS connections to the vendors' official https:// endpoints). Those use standard, publicly reviewed TLS.


    Enough for a badge!

    If the software produced by the project is an application or library, and its primary purpose is not to implement cryptography, then it SHOULD only call on software specifically designed to implement cryptographic functions; it SHOULD NOT re-implement its own. [crypto_call]

    The project does not implement any cryptography of its own. Its only use of cryptography, HTTPS, is delegated entirely to purpose-built implementations: Cloudflare's edge terminates TLS for the site, and outbound requests to vendors use the runtime's standard fetch (the Workers runtime or Node's built-in TLS). The source contains no hashing, encryption, signing or random-token code.S


    Enough for a badge!

    All functionality in the software produced by the project that depends on cryptography MUST be implementable using FLOSS. [crypto_floss]
    See the Open Standards Requirement for Software by the Open Source Initiative.

    Enough for a badge!

    The security mechanisms within the software produced by the project MUST use default keylengths that at least meet the NIST minimum requirements through the year 2030 (as stated in 2012). It MUST be possible to configure the software so that smaller keylengths are completely disabled. [crypto_keylength]
    These minimum bitlengths are: symmetric key 112, factoring modulus 2048, discrete logarithm key 224, discrete logarithmic group 2048, elliptic curve 224, and hash 224 (password hashing is not covered by this bitlength, more information on password hashing can be found in the crypto_password_storage criterion). See https://www.keylength.com for a comparison of keylength recommendations from various organizations. The software MAY allow smaller keylengths in some configurations (ideally it would not, since this allows downgrade attacks, but shorter keylengths are sometimes necessary for interoperability).

    Enough for a badge!

    The default security mechanisms within the software produced by the project MUST NOT depend on broken cryptographic algorithms (e.g., MD4, MD5, single DES, RC4, Dual_EC_DRBG), or use cipher modes that are inappropriate to the context, unless they are necessary to implement an interoperable protocol (where the protocol implemented is the most recent version of that standard broadly supported by the network ecosystem, that ecosystem requires the use of such an algorithm or mode, and that ecosystem does not offer any more secure alternative). The documentation MUST describe any relevant security risks and any known mitigations if these broken algorithms or modes are necessary for an interoperable protocol. [crypto_working]
    ECB mode is almost never appropriate because it reveals identical blocks within the ciphertext as demonstrated by the ECB penguin, and CTR mode is often inappropriate because it does not perform authentication and causes duplicates if the input state is repeated. In many cases it's best to choose a block cipher algorithm mode designed to combine secrecy and authentication, e.g., Galois/Counter Mode (GCM) and EAX. Projects MAY allow users to enable broken mechanisms (e.g., during configuration) where necessary for compatibility, but then users know they're doing it.

    Enough for a badge!

    The default security mechanisms within the software produced by the project SHOULD NOT depend on cryptographic algorithms or modes with known serious weaknesses (e.g., the SHA-1 cryptographic hash algorithm or the CBC mode in SSH). [crypto_weaknesses]
    Concerns about CBC mode in SSH are discussed in CERT: SSH CBC vulnerability.

    Enough for a badge!

    The security mechanisms within the software produced by the project SHOULD implement perfect forward secrecy for key agreement protocols so a session key derived from a set of long-term keys cannot be compromised if one of the long-term keys is compromised in the future. [crypto_pfs]

    Enough for a badge!

    If the software produced by the project causes the storing of passwords for authentication of external users, the passwords MUST be stored as iterated hashes with a per-user salt by using a key stretching (iterated) algorithm (e.g., Argon2id, Bcrypt, Scrypt, or PBKDF2). See also OWASP Password Storage Cheat Sheet. [crypto_password_storage]
    This criterion applies only when the software is enforcing authentication of users using passwords for external users (aka inbound authentication), such as server-side web applications. It does not apply in cases where the software stores passwords for authenticating into other systems (aka outbound authentication, e.g., the software implements a client for some other system), since at least parts of that software must have often access to the unhashed password.

    Enough for a badge!

    The security mechanisms within the software produced by the project MUST generate all cryptographic keys and nonces using a cryptographically secure random number generator, and MUST NOT do so using generators that are cryptographically insecure. [crypto_random]
    A cryptographically secure random number generator may be a hardware random number generator, or it may be a cryptographically secure pseudo-random number generator (CSPRNG) using an algorithm such as Hash_DRBG, HMAC_DRBG, CTR_DRBG, Yarrow, or Fortuna. Examples of calls to secure random number generators include Java's java.security.SecureRandom and JavaScript's window.crypto.getRandomValues. Examples of calls to insecure random number generators include Java's java.util.Random and JavaScript's Math.random.

  • Secured delivery against man-in-the-middle (MITM) attacks


    Enough for a badge!

    The project MUST use a delivery mechanism that counters MITM attacks. Using https or ssh+scp is acceptable. [delivery_mitm]
    An even stronger mechanism is releasing the software with digitally signed packages, since that mitigates attacks on the distribution system, but this only works if the users can be confident that the public keys for signatures are correct and if the users will actually check the signature.

    Distribution channels use HTTPS exclusively. [osps_br_03_02]


    Enough for a badge!

    A cryptographic hash (e.g., a sha1sum) MUST NOT be retrieved over http and used without checking for a cryptographic signature. [delivery_unsigned]
    These hashes can be modified in transit.

  • Publicly known vulnerabilities fixed


    Enough for a badge!

    There MUST be no unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days. [vulnerabilities_fixed_60_days]
    The vulnerability must be patched and released by the project itself (patches may be developed elsewhere). A vulnerability becomes publicly known (for this purpose) once it has a CVE with publicly released non-paywalled information (reported, for example, in the National Vulnerability Database) or when the project has been informed and the information has been released to the public (possibly by the project). A vulnerability is considered medium or higher severity if its Common Vulnerability Scoring System (CVSS) base qualitative score is medium or higher. In CVSS versions 2.0 through 3.1, this is equivalent to a CVSS score of 4.0 or higher. Projects may use the CVSS score as published in a widely-used vulnerability database (such as the National Vulnerability Database) using the most-recent version of CVSS reported in that database. Projects may instead calculate the severity themselves using the latest version of CVSS at the time of the vulnerability disclosure, if the calculation inputs are publicly revealed once the vulnerability is publicly known. Note: this means that users might be left vulnerable to all attackers worldwide for up to 60 days. This criterion is often much easier to meet than what Google recommends in Rebooting responsible disclosure, because Google recommends that the 60-day period start when the project is notified even if the report is not public. Also note that this badge criterion, like other criteria, applies to the individual project. Some projects are part of larger umbrella organizations or larger projects, possibly in multiple layers, and many projects feed their results to other organizations and projects as part of a potentially-complex supply chain. An individual project often cannot control the rest, but an individual project can work to release a vulnerability patch in a timely way. Therefore, we focus solely on the individual project's response time. Once a patch is available from the individual project, others can determine how to deal with the patch (e.g., they can update to the newer version or they can apply just the patch as a cherry-picked solution).

    Enough for a badge!

    Projects SHOULD fix all critical vulnerabilities rapidly after they are reported. [vulnerabilities_critical_fixed]

  • Other security issues


    Enough for a badge!

    The public repositories MUST NOT leak a valid private credential (e.g., a working password or private key) that is intended to limit public access. [no_leaked_credentials]
    A project MAY leak "sample" credentials for testing and unimportant databases, as long as they are not intended to limit public access.

    The project does not implement any cryptography of its own. Its only use of cryptography, HTTPS, is delegated entirely to purpose-built implementations: Cloudflare's edge terminates TLS for the site, and outbound requests to vendors use the runtime's standard fetch (the Workers runtime or Node's built-in TLS). The source contains no hashing, encryption, signing or random-token code.


 Analysis 8/8 ●

  • Static code analysis


    Enough for a badge!

    At least one static code analysis tool (beyond compiler warnings and "safe" language modes) MUST be applied to any proposed major production release of the software before its release, if there is at least one FLOSS tool that implements this criterion in the selected language. [static_analysis]
    A static code analysis tool examines the software code (as source code, intermediate code, or executable) without executing it with specific inputs. For purposes of this criterion, compiler warnings and "safe" language modes do not count as static code analysis tools (these typically avoid deep analysis because speed is vital). Some static analysis tools focus on detecting generic defects, others focus on finding specific kinds of defects (such as vulnerabilities), and some do a combination. Examples of such static code analysis tools include cppcheck (C, C++), clang static analyzer (C, C++), SpotBugs (Java), FindBugs (Java) (including FindSecurityBugs), PMD (Java), Brakeman (Ruby on Rails), lintr (R), goodpractice (R), Coverity Quality Analyzer, SonarQube, Codacy, and HP Enterprise Fortify Static Code Analyzer. Larger lists of tools can be found in places such as the Wikipedia list of tools for static code analysis, OWASP information on static code analysis, NIST list of source code security analyzers, and Wheeler's list of static analysis tools. If there are no FLOSS static analysis tools available for the implementation language(s) used, you may select 'N/A'.

    CodeQL static analysis (the javascript-typescript and actions query packs) runs on every pull request, on every push to dev, stage and main, and weekly. Its "CodeQL" check is required by the main branch ruleset, so no release can ship with an open finding. Biome's linter, zizmor (GitHub Actions security analysis), actionlint, shellcheck, Trivy (dependency and container scanning) and OpenSSF Scorecard also run in CI, and every release passes through all of them before it is tagged on main. https://github.com/greenblacked/status-page/blob/main/.github/workflows/codeql.yml


    Enough for a badge!

    It is SUGGESTED that at least one of the static analysis tools used for the static_analysis criterion include rules or approaches to look for common vulnerabilities in the analyzed language or environment. [static_analysis_common_vulnerabilities]
    Static analysis tools that are specifically designed to look for common vulnerabilities are more likely to find them. That said, using any static tools will typically help find some problems, so we are suggesting but not requiring this for the 'passing' level badge.

    CodeQL runs its security queries for JavaScript/TypeScript, which look for common vulnerabilities such as XSS, injection, prototype pollution, insecure randomness and unsafe URL handling, together with its GitHub Actions queries (untrusted checkout, cache poisoning, code injection in workflows). zizmor also checks the workflows for Actions-specific vulnerabilities such as template injection, excessive permissions and credential persistence. Findings surface as code-scanning alerts and fail the required CodeQL check. https://github.com/greenblacked/status-page/security/code-scanning


    Enough for a badge!

    All medium and higher severity exploitable vulnerabilities discovered with static code analysis MUST be fixed in a timely way after they are confirmed. [static_analysis_fixed]
    A vulnerability is considered medium or higher severity if its Common Vulnerability Scoring System (CVSS) base qualitative score is medium or higher. In CVSS versions 2.0 through 3.1, this is equivalent to a CVSS score of 4.0 or higher. Projects may use the CVSS score as published in a widely-used vulnerability database (such as the National Vulnerability Database) using the most-recent version of CVSS reported in that database. Projects may instead calculate the severity themselves using the latest version of CVSS at the time of the vulnerability disclosure, if the calculation inputs are publicly revealed once the vulnerability is publicly known. Note that criterion vulnerabilities_fixed_60_days requires that all such vulnerabilities be fixed within 60 days of being made public.

    Every medium-or-higher finding from static analysis has been fixed promptly.

    • CodeQL flagged the release workflow for untrusted checkout and cache poisoning (high). The patterns were analysed and judged not exploitable, because the job only checks out commits already on main, and the workflow was restructured anyway within the same day (PR #53).
    • Scorecard's Pinned-Dependencies findings were fixed by installing npm from a hash-locked lockfile (#53).
    • One documented exception: Trivy reports advisories (GHSA-qhr7-859c-m2p7, GHSA-6j4f-fj2g-mc7p, GHSA-rfgv-xxqx-mfg5) in the brace-expansion and undici copies bundled inside the npm CLI, which is used only as a build tool and is never shipped in the Worker. They are ignored narrowly (scoped to that one lockfile, expiring 2026-12-31), with the reasoning in SECURITY.md and CONTRIBUTING.md, until npm ships fixed copies.
      https://github.com/greenblacked/status-page/pull/53 and https://github.com/greenblacked/status-page/security/code-scanning

    Enough for a badge!

    It is SUGGESTED that static source code analysis occur on every commit or at least daily. [static_analysis_often]

    Static analysis runs on every commit. CodeQL (JavaScript/TypeScript and GitHub Actions queries) runs on every pull request and every push to dev, stage and main, plus a weekly scheduled scan. Biome lint, TypeScript strict type checking, shellcheck, actionlint and zizmor run in the CI workflow on every pull request and push, and dependency review runs on every pull request. https://github.com/greenblacked/status-page/blob/main/.github/workflows/codeql.yml and https://github.com/greenblacked/status-page/blob/main/.github/workflows/ci.yml


  • Dynamic code analysis


    Enough for a badge!

    It is SUGGESTED that at least one dynamic analysis tool be applied to any proposed major production release of the software before its release. [dynamic_analysis]
    A dynamic analysis tool examines the software by executing it with specific inputs. For example, the project MAY use a fuzzing tool (e.g., American Fuzzy Lop) or a web application scanner (e.g., OWASP ZAP or w3af). In some cases the OSS-Fuzz project may be willing to apply fuzz testing to your project. For purposes of this criterion the dynamic analysis tool needs to vary the inputs in some way to look for various kinds of problems or be an automated test suite with at least 80% branch coverage. The Wikipedia page on dynamic analysis and the OWASP page on fuzzing identify some dynamic analysis tools. The analysis tool(s) MAY be focused on looking for security vulnerabilities, but this is not required.

    Static analysis runs on every commit. CodeQL (JavaScript/TypeScript and GitHub Actions queries) runs on every pull request and every push to dev, stage and main, plus a weekly scheduled scan. Biome lint, TypeScript strict type checking, shellcheck, actionlint and zizmor run in the CI workflow on every pull request and push, and dependency review runs on every pull request. https://github.com/greenblacked/status-page/blob/main/.github/workflows/codeql.yml and https://github.com/greenblacked/status-page/blob/main/.github/workflows/ci.yml


    Enough for a badge!

    It is SUGGESTED that if the software produced by the project includes software written using a memory-unsafe language (e.g., C or C++), then at least one dynamic tool (e.g., a fuzzer or web application scanner) be routinely used in combination with a mechanism to detect memory safety problems such as buffer overwrites. If the project does not produce software written in a memory-unsafe language, choose "not applicable" (N/A). [dynamic_analysis_unsafe]
    Examples of mechanisms to detect memory safety problems include Address Sanitizer (ASAN) (available in GCC and LLVM), Memory Sanitizer, and valgrind. Other potentially-used tools include thread sanitizer and undefined behavior sanitizer. Widespread assertions would also work.

    The software is written entirely in TypeScript and runs on JavaScript runtimes (Node.js and Cloudflare Workers/workerd), which are memory-safe languages. The project produces no C, C++ or other memory-unsafe code. Dynamic testing still runs on every change: Playwright browser tests in Chromium and WebKit, axe accessibility scans, and smoke tests of the built server and Worker.


    Enough for a badge!

    It is SUGGESTED that the project use a configuration for at least some dynamic analysis (such as testing or fuzzing) which enables many assertions. In many cases these assertions should not be enabled in production builds. [dynamic_analysis_enable_assertions]
    This criterion does not suggest enabling assertions during production; that is entirely up to the project and its users to decide. This criterion's focus is instead to improve fault detection during dynamic analysis before deployment. Enabling assertions in production use is completely different from enabling assertions during dynamic analysis (such as testing). In some cases enabling assertions in production use is extremely unwise (especially in high-integrity components). There are many arguments against enabling assertions in production, e.g., libraries should not crash callers, their presence may cause rejection by app stores, and/or activating an assertion in production may expose private data such as private keys. Beware that in many Linux distributions NDEBUG is not defined, so C/C++ assert() will by default be enabled for production in those environments. It may be important to use a different assertion mechanism or defining NDEBUG for production in those environments.

    Dynamic analysis runs with extra checks that production does not have. The Vitest unit suite runs React and the other libraries in development mode, which turns on their internal invariant checks and warnings (keys, hooks rules, hydration). The Playwright browser suite fails any test that logs a console error or a hydration warning, and runs axe accessibility assertions and pixel-level contrast assertions on every appearance. Production builds use the optimised production mode with these development checks stripped.


    Enough for a badge!

    All medium and higher severity exploitable vulnerabilities discovered with dynamic code analysis MUST be fixed in a timely way after they are confirmed. [dynamic_analysis_fixed]
    If you are not running dynamic code analysis and thus have not found any vulnerabilities in this way, choose "not applicable" (N/A). A vulnerability is considered medium or higher severity if its Common Vulnerability Scoring System (CVSS) base qualitative score is medium or higher. In CVSS versions 2.0 through 3.1, this is equivalent to a CVSS score of 4.0 or higher. Projects may use the CVSS score as published in a widely-used vulnerability database (such as the National Vulnerability Database) using the most-recent version of CVSS reported in that database. Projects may instead calculate the severity themselves using the latest version of CVSS at the time of the vulnerability disclosure, if the calculation inputs are publicly revealed once the vulnerability is publicly known.

    No medium-or-higher vulnerabilities have been found by dynamic analysis. The Playwright browser suite, the axe accessibility scans and the post-build smoke tests (which check the security headers, the API, the feed, /metrics and /readyz) have reported no security findings. Any that are confirmed will be fixed as described in SECURITY.md.



You can use tools and AI systems to propose changes via a simple URL, such as https://www.bestpractices.dev/en/projects/15113/choose/edit?osps_ac_01_01_status=Met&osps_ac_01_01_justification=GitHub+enforced. See our automation proposals system for how to do that. 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 Serhii and the OpenSSF Best Practices badge contributors.

Project badge entry owned by: Serhii.
Entry created on 2026-09-30 16:33:01 UTC, last updated on 2026-09-30 17:41:51 UTC. Last achieved passing badge on 2026-09-30 17:41:51 UTC.