pi-outpost

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


These are the Baseline Level 2 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.

    Self-hosted web interface for the pi coding agent: chat, files, documents and an integrated terminal, with the agent's shell confined by OS sandboxes.

    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 15/19 ●

  • Controls


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

    https://github.com/laurentftech/pi-outpost/blob/main/.github/workflows/ci.yml
    GitHub Actions repository settings were checked on 2026-11-08: default_workflow_permissions=read and workflows cannot approve PRs. CI, release, Docker and CodeQL declare contents: read defaults. Write permissions are declared explicitly on the jobs that publish releases/images, attest provenance, update the coverage badge or upload security results. Scorecard has a read-only workflow default and explicitly scoped analysis-job permissions.



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

    https://github.com/laurentftech/pi-outpost/releases/tag/v0.61.0
    Official releases have unique Semantic Versioning identifiers, recorded in manifests and git tags (for example v0.61.0). The release workflow checks tag/package-version consistency and avoids republishing versions already on npm. Packages, executables, GitHub Releases and versioned container tags are associated with that version.



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

    Non-trivial release notes file in repository: https://github.com/laurentftech/pi-outpost/blob/main/CHANGELOG.md.
    CHANGELOG.md has a human-readable section per release (Added / Changed / Fixed), written for users, not a raw commit log. The release workflow refuses to publish a version without its changelog section, uses that section as the GitHub Release notes, and ships the changelog inside the package so the app shows it after an update. [release_notes]



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

    https://github.com/laurentftech/pi-outpost/blob/main/package-lock.json
    Workspace package.json manifests declare dependencies and package-lock.json records the resolved dependency graph in machine-readable JSON. [external_dependencies]



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

    https://github.com/laurentftech/pi-outpost/releases/tag/v0.61.0
    All five released software files (three platform executables and two MCP bundles) are covered by the signed SLSA provenance statement in pi-outpost-0.61.0.sigstore.json. On 2026-11-08 each downloaded file passed gh attestation verify against that bundle, repository laurentftech/pi-outpost, signer workflow .github/workflows/release.yml and source ref refs/tags/v0.61.0; GitHub-hosted runners were required. An altered MCP bundle was rejected. The certificate binds the release to commit d8928a87d57e419aab78a89756e5b64ce37898e0. npm packages are published through OIDC with provenance. Verification instructions: https://github.com/laurentftech/pi-outpost/blob/main/docs/sea-packaging.md#verify-a-download



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

    https://github.com/laurentftech/pi-outpost/blob/main/docs/development.md#dependency-maintenance
    Dependency choices and constraints are documented: jsdom is held for Blob/object-URL compatibility, TypeBox is pinned for validator-contract compatibility, and KaTeX overrides address a named advisory. CONTRIBUTING.md requires review of new install scripts and retention of third-party license notices. Dependencies are obtained through npm ci with committed manifests/lockfiles and integrity hashes; the pinned npm toolchain has its own lockfile. The guide documents how to update the toolchain, track upstream fixes and assess exceptions; Dependabot tracks advisories.



    The project documentation MUST include instructions on how to build the software, including required libraries, frameworks, SDKs, and dependencies. [OSPS-DO-07.01]
    It is recommended to publish this information alongside the project's contributor documentation, such as in CONTRIBUTING.md or other developer task documentation. This may also be documented using Makefile targets or other automation scripts.

    https://github.com/laurentftech/pi-outpost/blob/main/CONTRIBUTING.md#development-setup
    The development guide specifies Node.js 24, Git, npm 12.2.2, native dependency prerequisites, npm ci, development and build commands. Node 26 is used for release executables. The testing guide documents suite commands and Playwright installation.



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

    https://github.com/laurentftech/pi-outpost/blob/main/GOVERNANCE.md#roles
    The governance document identifies Laurent Francoise (laurentftech) as the sole person with repository write access and npm publication rights. The GitHub collaborator inventory checked on 2026-11-08 contained only laurentftech (administrator). Future roles/access must be documented before permission is granted.



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

    GOVERNANCE.md § Roles (https://github.com/laurentftech/pi-outpost/blob/main/GOVERNANCE.md#roles) lists the roles and their responsibilities. The maintainer (the only account with write access and npm publish rights) sets direction, reviews and merges, releases, handles vulnerability reports and enforces the code of conduct. Contributors propose changes by issue or pull request and get no access by contributing. New roles are documented there before any permission is granted. [roles_responsibilities]



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

    https://github.com/laurentftech/pi-outpost/blob/main/CONTRIBUTING.md#changes-and-tests

    CONTRIBUTING.md states the requirements for acceptable contributions: follow the surrounding TypeScript/React conventions, keep each PR focused, avoid unrelated formatting and dependency churn, and pass npm run typecheck (strict TypeScript), npm run lint (Oxlint, enforced in CI) and the server/UI test suites, plus the e2e suite for user-visible changes. Security-sensitive changes require negative-case tests and a review of the trust boundary ("Dependencies and security-sensitive changes"), and PRs must update affected documentation and include a Documentation impact note ("Pull requests"). What each check enforces is described in docs/quality.md. [contribution_requirements]



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

    https://github.com/laurentftech/pi-outpost/blob/main/CONTRIBUTING.md
    Contributions are licensed under MIT, but the contribution policy, CI workflows and active repository rules do not require contributors to assert legal authorization on every commit. No mandatory DCO/CLA or equivalent per-commit control is configured.



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

    https://github.com/laurentftech/pi-outpost/rules/22049027
    The active protect_main ruleset requires CI ok and Analyze (actions), Analyze (csharp), and Analyze (javascript-typescript), with an up-to-date branch and no bypass actors. CI ok fails when an applicable job fails or is cancelled. The documentation-only test exemption is explicitly documented in docs/quality.md.



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

    https://github.com/laurentftech/pi-outpost/blob/main/docs/quality.md#documentation-only-pull-requests
    Code PRs must pass automated test suites before merge through CI ok. Documentation-only PRs deliberately skip all test suites and can merge after classification and CodeQL. Therefore the literal requirement to run at least one automated test suite before every accepted commit is not met; post-merge tests on main do not close that pre-merge exception.



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

    https://github.com/laurentftech/pi-outpost/blob/main/docs/development.md#runtime-architecture
    Design documentation is distributed across the runtime architecture (UI/widget, Fastify/WebSocket, per-project sessions, embedded/RPC agent runtimes), sandboxing and configuration guides (tools, terminal, extensions, MCP and operator controls), openwebui-architecture.md (actors, components, end-to-end tool-call sequence, storage and trust), and claude-desktop.md (stdio MCP hosts, local revisioned stores and shared apps-core/posters components). These cover the standalone, embedded, Open WebUI and Claude Desktop distributions and their principal actors/actions.



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

    https://github.com/laurentftech/pi-outpost/blob/main/server/src/index.ts
    CLI, configuration, embedding and integration guides exist, and the Open WebUI server exposes an OpenAPI description. Comparing the actual HTTP routes against the documentation found GET /files/download implemented in server/src/index.ts but absent from the user/developer reference documents. There is also no complete external WebSocket message reference accompanying the protocol types. The requirement to document all external interfaces is consequently not met.



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

    https://github.com/laurentftech/pi-outpost/blob/main/SECURITY.md#relevant-security-boundaries
    Security assessment is recorded in the security-boundary policy, sandbox investigations and feature design risk analyses. The auth-token design assesses XSS token theft, intermediary URL logs, brute force and browser-origin attacks; document extraction designs assess hostile documents, path confinement and resource exhaustion. openwebui-architecture.md assesses forged/replayed identities, cross-user access, iframe isolation, scoped poster-save capabilities and unencrypted data at rest. The Docker design assesses namespace/procfs/network boundaries and records actual confinement probes. These assessments identify concrete impacts, mitigations and accepted limitations rather than relying on test pass counts alone.



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

    https://github.com/laurentftech/pi-outpost/blob/main/SECURITY.md#reporting-a-vulnerability
    A private coordinated disclosure process exists, but SECURITY.md explicitly says response/remediation times depend on availability and impact and no fixed deadline is promised. The required clear response timeframe is therefore not currently documented.



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

    URL : https://github.com/laurentftech/pi-outpost/security/advisories/new
    Private vulnerability reporting is enabled on the repository; SECURITY.md points to the private form and asks reporters to keep details out of public issues. [vulnerability_report_private]



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

    https://github.com/laurentftech/pi-outpost/blob/main/SECURITY.md#reporting-a-vulnerability
    The documented policy publishes a GitHub security advisory with its GHSA identifier when a confirmed pi-outpost vulnerability is fixed, requests a CVE, and records the identifiers and affected/fixed versions in a Security section of the release notes. This states the publication process and does not invent a previously published vulnerability.



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

Project badge entry owned by: Laurent.
Entry created on 2026-11-07 12:35:44 UTC, last updated on 2026-11-08 19:31:42 UTC. Last achieved passing badge on 2026-11-07 13:32:38 UTC.