ramascene-explorer

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 16003 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/16003/baseline)](https://www.bestpractices.dev/projects/16003)
or by embedding this in your HTML:
<a href="https://www.bestpractices.dev/projects/16003"><img src="https://www.bestpractices.dev/projects/16003/baseline"></a>


These are the Baseline Level 1 criteria. These are criteria version v2026.08.28.

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

        

 Basics

  • General

    Note that other projects may use the same name.

    Static explorer over precomputed RaMa-Scene scenario results on EXIOBASE 2011, with every number traced to a verified run

    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.

    My GitHub account signs in with two-factor authentication (a passkey or authenticator app, not SMS), which GitHub requires of everyone who contributes code, and I am the only person with write access. URL: https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/about-mandatory-two-factor-authentication


    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.

    Only I can add a collaborator, by an invitation the person must accept. I am the only collaborator, and no invitation is open. URL: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository


    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.

    The protect-main ruleset, active on the default branch with no bypass actors, requires a pull request for every change to main. It also requires linear history. The pull request rule is in since 2026-10-24. URL: https://github.com/simonvanlierde/ramascene-explorer/rules


    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.

    The same ruleset blocks deleting main and force-pushing to it. URL: https://github.com/simonvanlierde/ramascene-explorer/rules


    Enough for a badge!

    When a CI/CD pipeline operates on untrusted metadata, those parameters MUST be sanitized and validated prior to use in the pipeline. [OSPS-BR-01.01]
    CI/CD pipelines should sanitize (quote, escape or exit on expected values) all metadata inputs which correspond to untrusted sources. This includes data such as branch names, commit messages, tags, pull request titles, and author information.

    No workflow runs on pull_request_target or workflow_run, and no run: step expands branch names, titles or other event data into the shell. The one step that reads pull request data (dco.yml) passes it through environment variables. zizmor checks the workflows in the hygiene job. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/.github/workflows/dco.yml


    Enough for a badge!

    When a CI/CD pipeline operates on untrusted code snapshots, it MUST prevent access to privileged CI/CD credentials and assets. [OSPS-BR-01.03]
    CI/CD pipelines should isolate untrusted code snapshots from privileged credentials and assets. In particular, projects should be careful to ensure that workflows which build or execute code prior to review by a collaborator do not have access to CI/CD credentials.

    Pull request code runs under the pull_request trigger, which gives fork pull requests no secrets and a read-only token. Every workflow sets permissions: contents: read at the top, every checkout sets persist-credentials: false, and the Pages deploy is a manual start only, from main only. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/.github/workflows/ci.yml


    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.

    Every official channel is HTTPS only: the GitHub repository, issues and releases, the GitHub Pages site, and the Zenodo DOI. URL: https://github.com/simonvanlierde/ramascene-explorer


    Enough for a badge!

    When the project lists a URI as an official distribution channel, that channel MUST be protected from adversary-in-the-middle attacks using cryptographically authenticated channels. [OSPS-BR-03.02]
    Artifacts distributed by the project should be distributed through channels which ensure integrity and authenticity. Use of HTTPS for downloads, signed releases, or distribution through trusted package managers are all acceptable methods to protect against adversary-in-the-middle attacks.

    Distribution is over HTTPS only: the Pages site and the embodied.parquet release asset. The release asset also has a SHA-256 in Git that CI checks before every use. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/data/embodied.sha256


    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.

    GitHub secret scanning with push protection is on, so a push holding a known secret is refused. A betterleaks git hook scans staged changes. CI uses the job token and OIDC, so there are few secrets to leak. Gap: .gitignore does not list .env; adding it is one line. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/.pre-commit-config.yaml


    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.

    The README explains how to view, build and test it, and docs/ covers the page, the scenarios and the precompute. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/README.md


    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.

    CONTRIBUTING.md says to open an issue with what you did, what you expected, what happened and the version, and sends vulnerabilities to the private route. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/CONTRIBUTING.md


    Enough for a badge!

    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.

    GitHub issues and pull requests are the public place to discuss changes and problems. URL: https://github.com/simonvanlierde/ramascene-explorer/issues


    Enough for a badge!

    The project documentation MUST include an explanation of the contribution process, or clearly state that public contributions are not accepted [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.

    CONTRIBUTING.md explains how to set up, run the checks and sign off commits for a pull request. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/CONTRIBUTING.md


    Enough for a badge!

    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.

    The source code is under the MIT licence, which is OSI-approved. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/LICENSE


    Enough for a badge!

    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.

    The released page is MIT code. The result data is CC BY 4.0, the fonts are under the SIL OFL 1.1 and the map geometry is public domain. All are free licences, set out in the README's Licence section. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/README.md


    Enough for a badge!

    The license for the source code MUST be maintained in the corresponding repository's LICENSE file, COPYING file, LICENSES/ directory, or LICENSE/ directory. [OSPS-LE-03.01]
    Include the project's source code license in the project's LICENSE file, COPYING file, LICENSES/ directory, 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.

    The licence is in LICENSE at the repository root. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/LICENSE


    Enough for a badge!

    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.

    The tagged source of each release has LICENSE at its root. Gap, not blocking: the dist/ published to Pages and the embodied.parquet asset carry no licence file; the README states the licences. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/LICENSE


    Enough for a badge!

    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.

    The source is public at a fixed URL, which pyproject.toml, CITATION.cff, the Pages header link and the README point to. URL: https://github.com/simonvanlierde/ramascene-explorer


    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 history on GitHub records every change with its author and date, and each merged pull request stays public with its discussion. URL: https://github.com/simonvanlierde/ramascene-explorer/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.

    package.json and pyproject.toml list the direct dependencies, and pnpm-lock.yaml and uv.lock pin the full tree. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/package.json


    Enough for a badge!

    Projects with multiple repositories MUST document a list of codebases that are part of the project. [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.

    The project is one repository. brightway-check/ is a folder inside it, not a separate codebase. URL: https://github.com/simonvanlierde/ramascene-explorer/tree/main/brightway-check


    Enough for a badge!

    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.

    The repository holds no generated executables. dist/ and data/embodied.parquet are in .gitignore, and the Parquet file is a release asset that CI downloads and checks. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/.gitignore


    Enough for a badge!

    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.

    Every tracked file is text, except two small data and image files the control exempts or that are not libraries: tests/fixture-embodied.parquet (a synthetic test fixture built by tests/make_fixture_embodied.py) and public/og.png (the share-card image). A check-added-large-files hook stops large files. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/tests/make_fixture_embodied.py


    Enough for a badge!

    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.

    .github/SECURITY.md names the security contact: GitHub's private vulnerability reporting, which is on for the repository and reaches me, with an acknowledgement promised within 14 days. URL: https://github.com/simonvanlierde/ramascene-explorer/blob/main/.github/SECURITY.md



You can use tools and AI systems to propose changes via a simple URL, such as https://www.bestpractices.dev/en/projects/16003/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 Simon van Lierde and the OpenSSF Best Practices badge contributors.

Project badge entry owned by: Simon van Lierde.
Entry created on 2026-10-27 18:52:01 UTC, last updated on 2026-10-27 21:03:16 UTC. Last achieved passing badge on 2026-10-27 19:03:39 UTC.