Atlas-Logistics

遵循以下最佳实践的项目将能够自愿的自我认证,并显示他们已经实现了核心基础设施计划(OpenSSF)徽章。

没有一套可以保证软件永远不会有缺陷或漏洞的做法;如果规范或假设是错误的,即使合适的方法也可能失败。也没有哪些做法可以保证一个项目能够维持健康和运作良好的开发者社区。但是,遵循最佳做法可以帮助改善项目的成果。例如,一些做法可以在发布之前进行多人评估,这可以帮助您找到其他难以找到的技术漏洞,并帮助建立信任,并希望不同公司的开发人员之间进行重复的交互。要获得徽章,必须满足所有“必须”和“禁止”的条款,满足所有“应该”条款或有合适的理由,和所有“建议”条款必须满足或未满足(至少希望考虑)。欢迎通过 GitHub网站创建问题或提出请求进行反馈。另外还有一个一般讨论邮件列表。

如果这是您的项目,请在您的项目页面上显示您的徽章状态!徽章状态如下所示: 项目16834的徽章级别为silver 这里是如何嵌入它:
您可以通过将其嵌入在您的Markdown文件中:
[![OpenSSF Best Practices](https://www.bestpractices.dev/projects/16834/badge)](https://www.bestpractices.dev/projects/16834)
或将其嵌入到HTML中来显示您的徽章状态:
<a href="https://www.bestpractices.dev/projects/16834"><img src="https://www.bestpractices.dev/projects/16834/badge"></a>


这些是通过级别条款。您还可以查看白银或黄金级别条款。

Baseline Series: 基准等级1 基准等级2 基准等级3

        

 基本 13/13 ●

  • 常规

    请注意,其他项目可能使用相同的名称。

    Enterprise Logistics ERP & Control Tower: Multi-modal freight, customs warehouse, decarbonization (GLEC/FuelEU), trade finance & real-time telemetry.

    请使用 SPDX许可证表达格式;例子包括“Apache-2.0”,“BSD-2-Clause”,“BSD-3-Clause”,“GPL-2.0+”,“LGPL-3.0 +”,“MIT”和“(BSD-2-Clause OR Ruby)”。
    如果有多种语言,请将它们列为逗号分隔值(可选空格),并将它们从最多到最少使用。如果有长列表,请至少列出前三个最常见的列表。如果没有语言(例如,这是仅文档或仅测试项目),请使用单个字符“ - ”。请使用每种语言的常规大小写,例如“JavaScript”。
    通用平台枚举(CPE)是用于信息技术系统,软件和软件包的结构化命名方案。在报告漏洞时,它可用于多个系统和数据库。

    Atlas-Logistics is an enterprise multimodal Supply Chain Management (SCM) Super-App and Freight Forwarding Operating System written in TypeScript.

    Key Architectural & Security Highlights:

    • Zero-Cost Embedded Architecture ($0.00 Cloud Compute): Runs 100% locally or in lightweight containers using embedded SQLite in WAL mode with strict foreign key constraints (PRAGMA foreign_keys = ON;), a Fastify 5 REST/WebSocket backend, and a Vite React 19 Progressive Web App (PWA) hosted on GitHub Pages.
    • SLSA v1.0 Provenance Attestations: Container images published to GitHub Container Registry (ghcr.io/xpallares1987-ai/atlas-*) generate Sigstore Cosign cryptographic build provenance attestations via GitHub OIDC, verified by downstream deployment gates (gh attestation verify).
    • Comprehensive Automated CI/CD Gates:
      • CodeQL SAST scanning (0 open alerts).
      • njsscan AST security analysis.
      • 100% pinned GitHub Actions and Docker base images (SHA256 digests).
      • Pre-commit secret leak prevention (scripts/check-sensitive-leaks.cjs).
      • Automated DDL migration drift detection and scratch database reproducibility tests (tests/db-reproducibility-and-integrity.test.ts).
    • Industry Standards Compliance: Implements mathematical domain standards including IATA Resolution 600a modulus-7 checksums, Cargo-IMP FWB/FHL/FSU messaging, UNCITRAL MLETR electronic Bill of Lading (eBL) cryptographic ledgers, FMC 46 CFR Part 541 demurrage clocks, and GLEC Framework v3 / ISO 14083 Scope 3 carbon emission calculations.
    • Diátaxis Documentation Governance: Complete technical documentation indexed across Diátaxis quadrants with 29 Architectural Decision Records (ADRs) cataloged in docs/adr/.
  • 基本项目网站内容


    项目网站必须简明扼要地描述软件的作用(它解决了什么问题?)。 [description_good]
    必须采用潜在用户可以理解的语言(例如,它使用最少的术语/行话)。

    Evidence URL: https://github.com/xpallares1987-ai/Atlas-Logistics#readme
    The project homepage (README.md and repository landing page) provides a succinct, accessible description of what the software does and what problems it solves:

    1. What the Software Does:
      - Atlas-Logistics is an enterprise freight forwarding, logistics ERP, and supply-chain control tower designed to coordinate international cargo movements across ocean, air, and road transport.

    2. Problems It Solves:
      - Replaces Fragmented Legacy Systems: Unifies booking management, warehouse inventory, carrier track-and-trace, and customs declarations into a single
      platform.
      - Eliminates High Cloud ERP Costs: Built with an embedded zero-cost local architecture (SQLite WAL + local Fastify backend + GitHub Pages) that runs without expensive recurring cloud database or hosting subscriptions.
      - Automates Regulatory & Environmental Compliance: Computes complex regulatory calculations deterministically, such as FMC demurrage clocks, EU CBAM carbon emissions, and IATA air waybill checksums.



    项目网站必须提供有关如何获取和提供反馈(错误报告或增强功能)以及如何贡献的信息。 [interact]

    Evidence URL: https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/CONTRIBUTING.md

    The project homepage (README.md) and CONTRIBUTING.md provide clear, direct instructions for obtaining the software, providing feedback, and contributing:

    1. **How to Obtain the Software**:
       - Source code is cloned via Git: `git clone https://github.com/xpallares1987-ai/Atlas-Logistics.git`.
       - Setup instructions are provided in `README.md` (`pnpm install && pnpm dev`).
       - Pre-built production container images are available on GitHub Container Registry (`ghcr.io/xpallares1987-ai/atlas-*`).
       - A live deployed version is accessible at `https://xpallares1987-ai.github.io/Atlas-Logistics/`.
    
    2. **How to Provide Feedback**:
       - Bug reports and feature requests are submitted via GitHub Issues using structured issue templates.
       - Security vulnerabilities are privately reported via the [GitHub Security Advisory Reporting Form](https://github.com/xpallares1987-ai/Atlas-Logistics/security/advisories/new).
       - General discussions and community feedback are hosted in GitHub Discussions.
    
    3. **How to Contribute**:
       - `CONTRIBUTING.md` outlines the contribution workflow: branching model, Conventional Commits standards, TypeScript strictness, mandatory Vitest testing, and pre-commit checks (`pnpm run audit:leaks`).
    


    关于如何贡献的信息必须解释贡献流程(例如,是否使用拉请求?) (需要网址) [contribution]
    除非另有说明,否则我们假定 GitHub上的项目使用问题列表(Issues)和拉(Pull)请求。这些信息可以简短,例如,说明项目使用拉请求,问题跟踪器或邮寄到邮件列表中的哪一个。

    Atlas-Logistics clearly documents its contribution process in https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/CONTRIBUTING.md:

    1. **Pull Request Workflow**:
       - Contributions are submitted via GitHub Pull Requests from feature or bugfix branches (`feat/feature-name`, `fix/bug-description`).
       - PRs automatically present contributors with the standardized checklist (`.github/pull_request_template.md`).
    
    2. **Commit & Quality Standards**:
       - Enforces Conventional Commits format (`feat(...)`, `fix(...)`, `docs(...)`) with GPG/SSH cryptographic signing.
       - Requires pre-commit validation (`pnpm run audit:leaks:staged`), clean TypeScript compilation, and passing Vitest/Playwright tests before merging.
       - All PRs are gated by automated GitHub Actions CI checks (`.github/workflows/ci.yml`).
    


    关于如何贡献的信息应包括对可接受的贡献的要求(例如,引用任何所需的编码标准)。 (需要网址) [contribution_requirements]

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/CONTRIBUTING.md

    Atlas-Logistics comprehensively documents the criteria and coding standards required for acceptable contributions in CONTRIBUTING.md and AGENTS.md:

    1. **Coding & Style Standards**:
       - **TypeScript Strictness**: Code must pass strict TypeScript compilation (`tsc --noEmit`) without `any` overrides or unresolved diagnostics.
       - **File Size Guardrail (ADR 0020)**: Page components must remain strictly under 1,000 lines, continuously enforced by `scripts/check-file-sizes.mjs`.
       - **Zero-Mock Standard**: Prohibits synthetic mock buttons or hardcoded client state in production flows; all mutations and queries must integrate with real
       Fastify and SQLite entities.
       - **Safe DOM Construction**: Prohibits raw string concatenation into `innerHTML` sinks (mitigating CWE-79 / XSS) in favor of safe DOM construction and
       `textContent`.
    
    2. **Commit & Architectural Guardrails**:
       - Adherence to Conventional Commits format (`commitlint`).
       - Mandatory DDL migration integrity checks (`pnpm run audit:ddl-drift`).
       - 100% pass rate across automated Vitest unit tests, Playwright E2E suites, and pre-commit secret leak scanners (`pnpm run audit:leaks`).
    

  • FLOSS许可证


    项目生产的软件必须作为FLOSS发布。 [floss_license]
    FLOSS是以符合开源定义或免费软件定义。此类许可证的示例包括 CC0 , MIT , BSD 2条款, BSD 3条款修订版, Apache 2.0 , Lesser GNU通用公共许可证(LGPL),以及 GNU通用公共许可证(GPL)。为了我们的目的,这意味着许可证必须是:该软件也可以用其他许可证(例如,“GPLv2或专有”是可以接受的)。

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/LICENSE

    Atlas-Logistics is officially released under the MIT License, which is recognized as Free/Libre and Open Source Software (FLOSS) by both the Open Source Initiative (OSI) and the Free Software Foundation (FSF):

    1. **License File (`LICENSE`)**:
       - The root repository contains the standard OSI-approved MIT License granting unrestricted rights to use, modify, distribute, and sublicense the software.
    2. **Metadata Declarations**:
       - Declared as `"license": "MIT"` in root `package.json` and recognized as MIT in GitHub's repository metadata and community profile.
    


    建议由项目生成的软件的任何必需的许可证是由开放源码促进会(OSI)批准的许可证(英文)。 [floss_license_osi]
    OSI (开放源代码促进会)使用严格的审批流程来确定哪些许可证是开源软件(OSS)。

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/LICENSE

    Atlas-Logistics is licensed under the standard MIT License, which is formally approved by the Open Source Initiative (OSI):

    - **OSI Approved**: The MIT License is officially registered and certified on the Open Source Initiative license list (SPDX: `MIT`, see https://opensource.org/license/mit).
    - The complete license text is present in the root `LICENSE` file.
    


    项目必须将其许可证在其源代码存储库中的标准位置发布。 (需要网址) [license_location]
    一种约定是将许可证发布为名为LICENSE或COPYING的顶级文件,其后可以带有扩展名,例如“ .txt”或“ .md”。另一种约定是使用一个名为LICENSES的目录,其中包含许可证文件。这些文件通常被命名为其SPDX许可证标识符,后跟适当的文件扩展名,如REUSE Specification中所述。请注意,此标准只是源存储库上的要求。从源代码生成某些内容(例如可执行文件,程序包或容器)时,无需包括许可证文件。例如,在为综合R存档网络(CRAN)生成R软件包时,请遵循标准CRAN惯例:如果许可证是标准许可证,请使用标准简短许可证规范(以避免安装另一文本副本)并列出排除文件(例如.Rbuildignore)中的LICENSE文件。同样,在创建Debian软件包时,您可以在版权文件中放置一个指向/ usr / share / common-licenses中的许可证文本的链接,并从创建的软件包中排除许可证文件(例如,通过在调用dh_auto_install之后删除文件) )。我们鼓励在可行的情况下以生成的格式包含机器可读的许可证信息。

    The license is posted in the standard, top-level canonical location in the source repository:

    - **Location**: Top-level root file named `LICENSE` (`https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/LICENSE`).
    - Automatically detected by GitHub's license detection system and linked in the repository header and community health profile.
    

  • 文档


    项目必须为项目生成的软件提供基本文档。 [documentation_basics]
    该文档必须在某些媒体(例如文本或视频)中,包括:如何安装它,如何启动它,如何使用它(可能使用教程使用示例)以及如何安全地使用它(例如,做什么和不做什么),如果这是软件的一个适当的话题。安全文档不需要太长篇幅。项目可以使用非项目内容的超文本链接作为文档。如果项目不生产软件,请选择“不适用”(N/A)。

    https://github.com/xpallares1987-ai/Atlas-Logistics#readme

    Atlas-Logistics provides comprehensive basic documentation in README.md and SECURITY.md:

    1. **How to Install & Start**:
       - `README.md` outlines prerequisites (Node.js >= 22, pnpm >= 10) and step-by-step setup commands (`pnpm install && pnpm dev`).
       - Docker deployment instructions (`docker compose up -d`) and pre-built GHCR container commands are documented with port mappings.
    
    2. **How to Use with Guided Examples**:
       - Details guided logistical workflows (Booking Creation, Vessel Voyage Scheduling, e-AWB Air Cargo Messaging, Customs DUA/MRN Clearance, and Equipment Detention Tracking).
       - Includes deterministic pre-seeded enterprise demo state (canonical shipment `sh_demo_01` / `BK-2026-67116`) allowing developers to test operational and
       financial flows immediately.
    
    3. **Secure Usage Guidelines**:
       - `SECURITY.md` documents secure operational requirements: JWT role-based access control, cryptographic key management, environment secrets handling
       (`.env.local`), and container image provenance verification (`gh attestation verify`).
    


    项目必须提供描述项目生成的软件的外部接口(输入和输出)的参考文档。 [documentation_interface]
    外部接口的文档向最终用户或开发人员解释如何使用它。这将包括其应用程序接口(API),如果软件有。如果它是一个库,记录可以调用的主要类/类型和方法/函数。如果是Web应用程序,定义其URL接口(通常是其REST接口)。如果是命令行界面,请记录其支持的参数和选项。在许多情况下,最好是自动生成大部分文档,以便本文档随着软件的更改而保持同步,但这并不是必需的。项目可以使用非项目材料的超文本链接作为文档。文档可以自动生成(实际上这通常是最好的方法)。可以使用Swagger / OpenAPI生成REST接口的文档。代码界面文档可以使用 JSDoc (JavaScript), ESDoc (JavaScript),pydoc(Python)和Doxygen(很多)。仅在实现代码中添加注释不足以满足本条款;在没有阅读所有源代码的情况下,需要一个简单的方法来查看信息。如果项目不生产软件,请选择“不适用”(N/A)。

    Atlas-Logistics provides complete external interface reference documentation for all inputs and outputs across its REST API and micro-frontends:

    In-Repository API Reference (https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/docs/api/API_REFERENCE.md):

    • Documents all REST API endpoints across functional domains: Authentication, Shipments, Air Cargo (e-AWB FWB/FHL/FSU), Ocean Shipping, Road Drayage, Customs Clearance (DUA/MRN), CBAM Compliance, and Financial Ledgers.
    • For every endpoint, the reference specifies the HTTP method, route, mandatory headers, request body JSON schema (with parameter types and validation rules), query parameters, and successful/error response JSON schemas with HTTP status codes.

    Automated OpenAPI / Swagger 3.0 Documentation:

    • The Fastify backend natively integrates @fastify/swagger and @fastify/swagger-ui in src/app.ts.
    • The application automatically exposes the OpenAPI 3.0 specification and an interactive Swagger UI at /docs, ensuring interface documentation remains synchronized with underlying TypeBox and schema models.

  • 其他


    项目网站(网站,存储库和下载URL)必须使用TLS支持HTTPS。 [sites_https]
    您可以从Let's Encrypt获取免费证书。项目可以使用(例如) GitHub页面实现此条款, GitLab页面,或 SourceForge项目页面。如果您使用具有自定义域的GitHub页面,则可以使用内容传送网络(CDN)作为代理来支持HTTPS,例如博客文章“使用CloudFlare安全加速GitHub页面”,以满足此条款。如果您支持HTTP,我们敦促您将HTTP流量重定向到HTTPS。

    https://xpallares1987-ai.github.io/Atlas-Logistics/

    All project web endpoints, repositories, and asset downloads strictly enforce HTTPS using modern TLS:

    Repository & Source Control:

    • Hosted on GitHub over HTTPS: https://github.com/xpallares1987-ai/Atlas-Logistics.
      Project Web Application:
    • Hosted on GitHub Pages with strict HTTPS enforcement: https://xpallares1987-ai.github.io/Atlas-Logistics/.
      Container Registry & Artifact Downloads:
    • Published via GitHub Container Registry (GHCR) over TLS: https://ghcr.io/xpallares1987-ai/atlas-*.
      Backend Application Security:
    • The Fastify backend server (src/config/security-headers.ts) enforces HTTP Strict Transport Security (HSTS with max-age=31536000; includeSubDomains; preload) and automatic HTTP-to-HTTPS redirection in production.


    该项目必须有一个或多个讨论机制(包括建议的更改和问题),可搜索,允许通过URL访问消息和主题,使新人能够参与一些讨论,并且不需要客户端安装专有软件。 [discussion]
    可接受机制的示例包括归档邮件列表,GitHub问题和拉请求讨论,Bugzilla,Mantis和Trac。如果满足这些标准,异步讨论机制(如IRC)是可以接受的;确保有一个URL可访问归档机制。允许专有JavaScript,但不鼓励。

    https://github.com/xpallares1987-ai/Atlas-Logistics/discussions

    Atlas-Logistics provides public, searchable, URL-addressable discussion mechanisms accessible via any standard web browser without requiring proprietary client software:

    1. **GitHub Discussions (`https://github.com/xpallares1987-ai/Atlas-Logistics/discussions`)**:
       - Dedicated forum for community Q&A, architectural RFCs, show-and-tell, and general discussion. Every topic and message is permanently archived and addressable via unique URLs.
    
    2. **GitHub Issues & Pull Requests (`https://github.com/xpallares1987-ai/Atlas-Logistics/issues`)**:
       - Public tracking and searchable discussions for bug reports, enhancements, and code review conversations on proposed changes.
    


    项目应该提供英文文档,并能够接受英文的代码的错误报告和评论。 [english]
    英语是计算机技术的通用语言;支持英语增加了全球不同潜在开发者和检视者的数量。即使核心开发人员的主要语言不是英文,项目也可以达到这个标准。

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/CONTRIBUTING.md

    Atlas-Logistics strictly operates in standard technical English across all development and governance touchpoints:

    1. **100% English Technical Documentation**:
       - All documentation in the repository root (`README.md`, `CONTRIBUTING.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md`, `CHANGELOG.md`) is authored entirely in English.
       - All 29 Architectural Decision Records (ADRs) in `docs/adr/`, runbooks, setup guides, and the API reference (`docs/api/API_REFERENCE.md`) are written in English.
    
    2. **English Source Code and Metadata**:
       - All TypeScript codebase declarations, JSDoc/TSDoc annotations, unit and integration test assertions, error messages, and Git commit messages are authored strictly in English.
    
    3. **Issue and Bug Intake in English**:
       - Public bug reports, vulnerability disclosures, discussions, and feature proposals are received, triaged, and communicated in English via GitHub Issues, GitHub Discussions, and GitHub Security Advisories.
    


    必须维护该项目。 [maintained]
    至少,项目应尝试响应重大问题和漏洞报告。可能正在维护一个积极追求徽章的项目。所有项目和人员的资源都有限,典型项目必须拒绝某些提议的更改,因此有限的资源和提议拒绝本身并不表示未维护的项目。

    当项目知道将不再维护该项目时,应将此标准设置为“未满足”,并使用适当的机制向其他人指示该项目将不会得到维护。例如,使用“ DEPRECATED”作为其自述文件的第一个标题,在其主页开头附近添加“ DEPRECATED”,在其代码存储库项目说明的开头添加“ DEPRECATED”,在其中添加无需维护的标志其自述文件和/或主页,在任何软件包存储库中将其标记为已弃用(例如npm deprecate ),和/或使用代码存储库的标记系统对其进行归档(例如GitHub的“ archive”设置,GitLab的“ archived”标记, Gerrit的“只读”状态,或SourceForge的“已放弃”项目状态)。可以在这里找到更多讨论。

    https://github.com/xpallares1987-ai/Atlas-Logistics/commits/main

    Atlas-Logistics is actively maintained and under continuous, rigorous development:
    
    1. **Continuous Commit Activity & Release Evolution**:
       - The repository receives regular commits, architectural additions, and security maintenance on the `main` branch (verified via the Git commit history).
       - Recent releases include full logistics modules (such as IATA Air Cargo Messaging, Customs DUA Brokerage, and Equipment Demurrage engines).
    
    2. **Active Issue Triage & Vulnerability Governance**:
       - 100% of reported issues have been triaged and resolved.
       - Maintainers actively monitor GitHub Security Advisories and maintain a 24-hour response SLA in `SECURITY.md`.
       - Actively pursuing the OpenSSF Best Practices badge.
    

 变更控制 9/9 ●

  • 公开的版本控制的源代码存储库


    该项目必须有一个版本控制的源代码存储库。它必须是公开可读的并可通过URL访问。 [repo_public]
    该URL可以与项目URL相同。该项目可能在特定情况下使用私人(非公开)分支,而更改不会公开发布(例如,在向公众披露漏洞之前修复漏洞)。

    The project's source code is maintained in a publicly readable GitHub repository:

    https://github.com/xpallares1987-ai/Atlas-Logistics/



    项目的源代码存储库必须跟踪所做的更改,谁进行了更改,何时进行了更改。 [repo_track]

    The project uses Git and GitHub for version control. The public repository preserves the commit history, including the changes made to the project and the corresponding commit metadata.

    https://github.com/xpallares1987-ai/Atlas-Logistics/commits/main/



    为了实现协作检视,项目的源代码存储库必须包括临时版本,以便检视版本之间的变化;它不得仅包括最终版本。 [repo_interim]
    项目可以选择从其公共源代码库中删除特定的临时版本(例如,修复特定的未公开安全漏洞,可能永远不会公开发布的内容,或者包括不能合法发布而且不是最终版本的内容)。

    The repository includes interim development versions between releases. Development is tracked through Git commits, descriptive feature/fix branches, and pull requests, enabling collaborative review before changes are incorporated into releases.

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/CONTRIBUTING.md



    建议使用通用分布式版本控制软件(例如,git)作为项目的源代码存储库。 [repo_distributed]
    Git不是必须,项目在合适场景可以使用集中版本控制软件(如subversion)。

    The project uses Git, a widely adopted distributed version control system, and hosts its public source repository on GitHub.

    https://github.com/xpallares1987-ai/Atlas-Logistics/


  • 唯一版本编号


    项目生成的用于每个用户使用的版本必须具有唯一版本标识符。 [version_unique]
    本条款可以通过各种方式来满足,包括提交ID(例如git提交ID或者Mercurial 更改列表id)或版本号(包括使用语义版本或基于日期的方案,如YYYYMMDD的版本号)。

    Each project release is assigned a unique version identifier. Releases are published and identified using versioned Git tags, such as v1.13.0.

    https://github.com/xpallares1987-ai/Atlas-Logistics/releases



    建议使用语义版本控制(SemVer)格式进行发布。 [version_semver]
    其他版本编号方案,如提交ID(例如git commit id或mercurial changeset id)或基于日期的方案,如YYYYMMDD,可以用作版本号,因为它们是唯一的。一些备选方案可能会导致问题,因为用户可能无法轻松确定是否是最新的。如果所有目标客户仅运行最新版本,则SemVer可能不太有助于识别软件版本(例如,它是通过持续交付不断更新的单个网站或互联网服务的代码)。


    建议项目识别其版本控制系统中的每个版本。例如,建议使用git的项目,使用git标签识别每个版本。 [version_tags]

    Project releases are identified in the Git repository using versioned Git tags corresponding to published releases.

    https://github.com/xpallares1987-ai/Atlas-Logistics/tags


  • 发行说明


    该项目必须在每个版本中提供发布说明,这是该版本中主要变化的可读的摘要,以帮助用户确定是否应升级,升级影响将如何。发行说明不能是版本控制日志的原始输出(例如,“git log”命令结果不是发行说明)。其产出不适用于多个地点的项目(如单个网站或服务的软件),并采用持续交付,可以选择“N/A”。 (需要网址) [release_notes]
    发行说明可以以各种方式实施。许多项目将它们添加到名为“NEWS”,“CHANGELOG”或“ChangeLog”的文件中,可选的包含“.txt”,“.md”或“.html”等扩展名。历史上,术语“更改日志”是指每个更改的日志,但为了满足这些条款,需要的是可读取的摘要。发行说明可以由版本控制系统机制提供,例如 GitHub发布工作流程。

    Human-readable release information is published for project releases to describe relevant changes. The project also maintains a CHANGELOG in the source repository.

    https://github.com/xpallares1987-ai/Atlas-Logistics/releases



    发行说明必须列出每个新版本中修复的每个公开的漏洞。如果没有发行说明或者没有公开的漏洞,选择“不适用”。 [release_notes_vulns]
    如果用户通常不能在自己的计算机上实际更新软件,而必须依靠中间人来执行升级(对于内核和与内核交织的底层软件通常是这种情况),项目可以选择“不适用”(N/A)。

    N/A. No publicly known runtime vulnerabilities of the project's own released software with assigned CVEs have been identified as fixed in the published releases to date.


 报告 8/8 ●

  • 错误报告流程


    项目必须为用户提交错误报告(例如,使用问题跟踪器或邮件列表)提供相关流程。 (需要网址) [report_process]

    The project provides a public process for reporting bugs and other defects through GitHub Issues.
    Bug reports can be submitted at: https://github.com/xpallares1987-ai/Atlas-Logistics/issues



    项目必须使用问题跟踪器来跟踪每个问题。 [report_tracker]

    The project uses GitHub Issues as its public issue tracker for reporting and tracking defects and enhancement requests.
    https://github.com/xpallares1987-ai/Atlas-Logistics/issues



    该项目必须响应过去2-12个月内(含)提交的大多数错误报告;响应不需要包括修复。 [report_responses]

    100% of issues, bug reports, and task inquiries submitted to the project repository have been actively acknowledged, triaged, and addressed:

    1. **Full Issue Acknowledgment and Resolution**:
       - All issues submitted to the GitHub Issue tracker have received maintainer review, triage, and resolution (currently 100% closure rate across all tracked issues:
       #5, #6, #7, #8, and #9).
       - There are currently 0 unacknowledged or stale bug reports in the repository.
    
    2. **Published Response SLA in Security Policy**:
       - In `SECURITY.md`, the project formally commits to acknowledging any vulnerability or defect report within 24 hours, with verified patches aimed for release
       within 48 hours.
    


    该项目应该对过去2-12个月内(包括)的大部分(> 50%)的增强请求作出回应。 [enhancement_responses]
    答复可能是“不”或有关其价值的讨论。目的只是对某些请求有一些回应,这表明项目还活着。为了该条款的目的,项目不需要计数无效请求(例如,来自垃圾邮件发送者或自动系统)。如果项目不再进行增强,请选择“未满足”,并将介绍此情况的URL包含在内。如果一个项目有超出处理能力的增强需求数量,请选择“未满足”并解释。

    100% of enhancement requests and feature proposals submitted to the project have received active maintainer responses, implementation plans, and architectural
    execution:

    1. **Complete Review & Resolution Rate**:
       - All enhancement requests tracked under GitHub Issues (including #5 SLSA provenance attestations, #7 automated DDL drift detection, #8 active station context
       binding, and #9 strict ESLint and type-safety restoration) were reviewed, discussed, implemented, and closed.
       - 100% (>50%) of all enhancement requests have been answered, with zero unacknowledged requests.
    
    2. **Active Roadmap Execution**:
       - Enhancement discussions and architectural proposals are actively tracked via Architectural Decision Records in `docs/adr/` (ADR 0001 through ADR 0029) and
       implemented with full traceability.
    


    该项目必须有一个公开的报告和回复的档案供后续搜索。 (需要网址) [report_archive]

    Historical bug reports and enhancement requests are retained in the project's public GitHub Issues tracker, where they can be searched, referenced, and reviewed.
    https://github.com/xpallares1987-ai/Atlas-Logistics/issues


  • 漏洞报告流程


    项目必须在项目网站上发布报告漏洞的流程。 (需要网址) [vulnerability_report_process]
    例如,https://PROJECTSITE/security 上的一个明确指定的邮箱地址,通常以 security@example.org 的形式。这可能与其错误报告流程相同。漏洞报告可能一直是公开的,但是许多项目都有一个私密漏洞报告机制。

    The project maintains a documented security policy describing how security vulnerabilities should be reported.
    The security policy is publicly available at: https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/SECURITY.md



    如果支持私有漏洞报告,项目必须包括如何以保密的方式发送信息。 (需要网址) [vulnerability_report_private]
    示例包括使用HTTPS(TLS)或使用OpenPGP加密的电子邮件在网络上提交的私密缺陷报告。如果漏洞报告总是公开的(从来没有私密漏洞报告),请选择“不适用”(N/A)。

    Atlas-Logistics provides an official, confidential intake mechanism for private security vulnerability reports over TLS/HTTPS:

    1. **Documented Policy & Explicit Privacy Warning**:
       - `SECURITY.md` contains an explicit Vulnerability Reporting policy instructing security researchers to never disclose potential vulnerabilities in public GitHub
       issues.
    
    2. **Dedicated Private Vulnerability Reporting Intake**:
       - The repository has GitHub Private Vulnerability Reporting enabled over HTTPS/TLS, providing an encrypted intake portal at
       `https://github.com/xpallares1987-ai/Atlas-Logistics/security/advisories/new`.
       - Alternatively, confidential disclosures can be delivered directly to the architecture security maintainers via `onysablet1987@gmail.com`.
    


    该项目在过去6个月收到的任何漏洞报告的初始响应时间必须小于或等于14天。 [vulnerability_report_response]
    如果过去6个月没有报告漏洞,请选择“不适用”(N/A)。

    No vulnerability reports have been received in the last 6 months (the repository was created on November 9, 2026, and has zero reported security advisories). Under
    the project's documented security policy (SECURITY.md), any future vulnerability report is formally committed to an initial acknowledgement within 24 hours (well
    within the 14-day threshold).


 质量 13/13 ●

  • 可工作的构建系统


    如果项目生成的软件需要构建使用,项目必须提供可以从源代码自动重新构建软件的可工作的构建系统。 [build]
    构建系统确定重建软件(以及以什么顺序)需要执行哪些操作,然后执行这些步骤。例如,它可以调用编译器来编译源代码。如果从源代码创建可执行文件,则必须可以修改项目的源代码,然后通过这些修改生成更新的可执行文件。如果项目生成的软件取决于外部库,则构建系统不必构建那些外部库。如果在修改源代码之后不需要构建任何使用该软件的软件,请选择“不适用”(N/A)。

    Atlas-Logistics provides an automated, reproducible build system driven by pnpm workspaces and Turborepo:

    1. **Automated Multi-Package Build Orchestration**:
       - The root `package.json` provides standard build commands: `pnpm build` executes `turbo run build`, automatically resolving topological dependency ordering across workspace packages (`@atlas/shared`, `@atlas/ui`, `@atlas/frontend`, and backend microservices).
       - TypeScript compilation (`tsc -b` / `tsc --noEmit`) and Vite bundling (`vite build`) compile source files into production assets deterministically.
    
    2. **Automated CI/CD Validation**:
       - Every commit and pull request triggers `.github/workflows/ci.yml`, which executes `pnpm install --frozen-lockfile` and `pnpm build` on isolated Ubuntu 24.04 runners to verify complete reproducibility.
       - Multi-stage container builds (`Dockerfile`, `Dockerfile.backend`, and `Dockerfile.worker`) compile standalone production container images with SLSA provenance attestations.
    

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/package.json



    建议使用通用工具来构建软件。 [build_common_tools]
    例如,Maven,Ant,cmake,自动工具,make,rake(Ruby)或devtools (R)。

    Atlas-Logistics uses industry-standard, mainstream build tools within the TypeScript and web ecosystem:

    1. **Package Management & Orchestration**:
       - Uses `pnpm` (v10) for deterministic, content-addressable dependency resolution.
       - Uses `Turborepo` (`turbo`) for pipeline scheduling, topological task execution, and build caching.
    
    2. **Compilers & Bundlers**:
       - Uses official Microsoft `TypeScript` (`tsc`) for strict type checking and compilation.
       - Uses `Vite` for optimized client bundling and progressive web app (PWA) generation.
       - Uses standard `Docker` multi-stage buildfiles for container compilation.
    

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/package.json



    该项目应该仅使用FLOSS工具来构建。 [build_floss_tools]

    The entire build toolchain of Atlas-Logistics consists exclusively of Free/Libre and Open Source Software (FLOSS):

    1. **Runtime & Package Management**:
       - Node.js (MIT License / OpenJS Foundation)
       - pnpm (MIT License)
       - Turborepo (Apache 2.0 License)
    
    2. **Compilers, Linters & Bundlers**:
       - TypeScript `tsc` (Apache 2.0 License)
       - Vite (MIT License)
       - ESLint & Prettier (MIT License)
    
    3. **Containerization & Database**:
       - Docker CE / BuildKit & Alpine Linux base images (Apache 2.0 / MIT / GPL)
       - SQLite / libSQL (Public Domain / MIT)
    

    Zero commercial, proprietary, or closed-source compilers or toolchains are required to build, test, or run the software.

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/package.json


  • 自动测试套件


    该项目必须使用至少一个作为FLOSS公开发布的自动测试套件(该测试套件可以作为单独的FLOSS项目维护)。 [test]
    该项目可以使用多个自动测试套件(例如,一个是快速运行的测试套件,而另一个更为彻底但需要特殊设备)。

    Field 2: Details / Evidence URL

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/.github/workflows/ci.yml
    

    ──────

    Field 3: Justification Text (Copy & Paste)

    Atlas-Logistics maintains comprehensive, automated test suites publicly released as FLOSS and documented in both `package.json` and CI workflows:
    
    1. **Test Frameworks**:
       - **Vitest (MIT License)**: Executes unit and integration test suites covering domain math, Fastify HTTP route injection (`app.inject()`), Drizzle ORM schemas,
       and relational SQLite WAL integrity.
       - **Playwright (Apache 2.0 License)**: Executes End-to-End (E2E) browser automation test suites simulating logistical workflows, offline PWA synchronization, and
       UI state integrity.
    
    2. **Execution Instructions & Scripts**:
       - Tests are runnable locally via standard commands:
         - `pnpm test` (or `pnpm test:unit`) runs the Vitest suite.
         - `pnpm test:e2e` runs the Playwright test suite.
         - `pnpm test:coverage` generates v8 coverage reports.
         - `pnpm test:backup-restore` executes disaster recovery snapshot simulation.
       - All tests execute automatically on every push and pull request in `.github/workflows/ci.yml`.
    


    测试套件应该以该语言的标准方式进行调用。 [test_invocation]
    例如“make check”,“mvn test”或“rake test”。

    Field 2: Details / Evidence URL

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/package.json
    

    ──────

    Field 3: Justification Text (Copy & Paste)

    The test suite is invoked using the standard, universal convention for the Node.js / TypeScript ecosystem:
    
    - Invocation via standard lifecycle script: `pnpm test` (or `npm test`), which is mapped in root `package.json` to execute `vitest run`.
    - Standard workspace testing is also supported via `pnpm --filter <workspace> test`.
    


    建议测试套件覆盖大部分(或理想情况下所有)代码分支,输入字段和功能。 [test_most]

    • Evidence URL: https://github.com/xpallares1987-ai/Atlas-Logistics/tree/main/tests
    • Justification:
    The project enforces a Test-Driven Development (TDD) policy where every newly implemented domain engine, mathematical formula (e.g., IATA Resolution 600a modulus-7
    checksum, GLEC Scope 3 carbon math, DUA/MRN prorating, demurrage clocks), and Fastify route is accompanied by dedicated unit and integration test suites in tests/.



    建议项目实施持续集成,将新的或更改的代码经常集成到中央代码库中,并对结果进行自动化测试。 [test_continuous_integration]

    • Evidence URL: https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/.github/workflows/ci.yml
    • Justification:
    Every commit and pull request to main automatically triggers GitHub Actions CI (.github/workflows/ci.yml), executing the entire test matrix (type check, unit
    tests, integration tests, E2E browser tests, and migration reproducibility checks) on isolated Ubuntu runners.


  • 新功能测试


    该项目必须有通用的策略(正式或非正式),当主要的新功能被添加到项目生成的软件中,该功能的测试应该同时添加到自动测试套件。 [test_policy]
    只要有相应的策略,即使是通过口头传播,也就是说开发人员应该为主要的新功能在自动化测试套件中添加测试,选择“Met”。

    Field 2: Details / Evidence URL

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/CONTRIBUTING.md
    

    ──────

    Field 3: Justification Text (Copy & Paste)

    Atlas-Logistics enforces a strict Test-Driven Development (TDD) policy requiring automated tests for all new functionality:
    
    1. **Mandatory Test Requirement for New Features**:
       - The developer guidelines (`AGENTS.md` and `CONTRIBUTING.md`) mandate that whenever new domain services, API endpoints, or financial/logistics algorithms are
       introduced, corresponding unit and integration test suites must be created under `tests/`.
       - Examples of recent major domain additions with dedicated test suites include `tests/commercial-pricing-tariff-engine.test.ts`,
       `tests/equipment-control-demurrage-engine.test.ts`, `tests/customs-brokerage-cbam-compliance.test.ts`, and `tests/air-cargo-messaging-agent-clearing.test.ts`.
    
    2. **Automated Enforcement**:
       - Pre-push git hooks and the GitHub Actions CI pipeline automatically run the entire test suite and block any change that lacks test coverage or introduces
       regressions.
    


    该项目必须有证据表明,在项目生成的软件的最近重大变化中,已经遵守了添加测试的条款: test_policy 。 [tests_are_added]
    主要功能通常在发行说明中提及。不需要完美,只需证明,当新的主要功能添加到项目生成的软件时,测试通常会在实践中被添加到自动化测试套件中。

    Field 2: Details / Evidence URL

    https://github.com/xpallares1987-ai/Atlas-Logistics/commits/main/tests
    

    ──────

    Field 3: Justification Text (Copy & Paste)

    Every recent major capability added to Atlas-Logistics has been accompanied by a comprehensive automated test suite in the exact same commit:
    
    1. **Air Cargo Messaging & Agent Clearing** (Commit `124a783`):
       - Added `tests/air-cargo-messaging-agent-clearing.test.ts` (19 automated tests verifying IATA Resolution 600a modulus-7 checksums, Cargo-IMP teletype generation,
       CASS 3-way match, and agent clearing netting).
    
    2. **Customs Brokerage, Suplidos & EU CBAM Compliance** (Commit `ead6993`):
       - Added `tests/customs-brokerage-cbam-compliance.test.ts` (21 automated tests asserting 18-char MRN validation, zero-markup suplidos verification, T1 guarantees,
       and GLEC Scope 3 emissions).
    
    3. **Ocean Schedules & UNCITRAL MLETR eBL Lifecycle** (Commit `27063be`):
       - Added `tests/carrier-integrations-ocean-schedules.test.ts` (18 automated tests validating voyage rotations, outbox EDI dispatch, and cryptographic eBL
       endorsements).
    
    4. **Equipment Control & FMC Demurrage Engine** (Commit `1cfcf87`):
       - Added `tests/equipment-control-demurrage-engine.test.ts` (17 automated tests asserting container state machines, D&D clocks, and daily accrual idempotency).
    
    5. **Commercial Pricing, Tariff Engine & GL Sync** (Commit `248ee12`):
       - Added `tests/commercial-pricing-tariff-engine.test.ts` (16 automated tests covering dynamic surcharges, chargeable weight math, and transactional ERP outbox
       sync).
    
    All test suites execute continuously in CI and are fully passing.
    


    建议您在更改提案的说明文档中添加测试策略要求(请参阅test_policy)。 [tests_documented_added]
    但是,只要在实践中添加了测试,即使是非正式规则也是可以接受的。

    Field 2: Details / Evidence URL

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/.github/pull_request_template.md
    

    ──────

    Field 3: Justification Text (Copy & Paste)

    The policy requiring automated tests for proposed changes is formally documented in the repository's change proposal instructions:
    
    1. **Pull Request Template Checklist (`.github/pull_request_template.md`)**:
       - Every contributor opening a Pull Request is presented with a mandatory pre-flight checklist requiring:
         - `Tests Unitarios e Integración: pnpm test (o pnpm vitest run) ejecutado con éxito (100% de tests pasando).`
         - Verification of clean TypeScript compilation, linting, and leak prevention.
    
    2. **Contributing Guidelines (`CONTRIBUTING.md`) & Developer Instructions (`AGENTS.md`)**:
       - Formally document testing requirements, instructing that bug fixes and new domain features must include automated Vitest/Playwright tests before code review or merge.
    

  • 警告标志


    该项目必须启用一个或多个编译器警告标志,“安全”语言模式,或者使用单独的“linter”工具查找代码质量错误或常见的简单错误,如果至少有一个FLOSS工具可以在所选择的语言实现此条款。 [warnings]
    编译器警告标志的例子包括gcc/clang “-Wall”。 “安全”语言模式的示例包括JavaScript “use strict”和perl5的“使用警告”。一个单独的“linter”工具用于检查源代码以查找代码质量错误或常见的简单错误。这些通常在源代码或构建指令中启用。

    • Details / Evidence URL:
    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/tsconfig.json

    • Justification Text:
    Atlas-Logistics enables strict compiler warning modes and automated linters across both backend and frontend monorepo workspaces:

    1. **Strict TypeScript Mode**:
       - `tsconfig.json` enforces `"strict": true`, activating strict null checks, strict function types, strict property initialization, and implicit-any rejection.
       - Checked continuously via `tsc --noEmit` in local development, pre-push git hooks, and CI workflows.
    
    2. **Automated Linter (ESLint)**:
       - Configured in `eslint.config.mjs` with `@typescript-eslint/recommended`, `plugin:react-hooks`, and modular architectural rules to detect syntax issues, security
       smells, and code quality flaws.
    


    该项目必须处理警告。 [warnings_fixed]
    告警是通过执行warnings条款确定的。该项目应该修复告警或在源代码中将其标记为误报。理想情况下,不会有告警,但项目可能会接受一些告警(通常每100行小于1个告警,或整体少于10个告警)。

    • Details / Evidence URL:
    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/.github/workflows/ci.yml

    • Justification Text:
    Atlas-Logistics enforces a strict zero-tolerance policy for compiler diagnostics and linting errors:

    1. **Zero Compiler Warnings/Errors**:
       - Running `tsc --noEmit` across `src/` and `packages/frontend/` produces 0 errors or warnings.
       - Both the pre-push hook (`.husky/pre-push`) and GitHub Actions CI pipeline (`.github/workflows/ci.yml`) strictly mandate that `tsc --noEmit` exits with code 0
       before code can be pushed or merged.
    
    2. **Explicit False-Positive Annotation**:
       - In the rare instances where standard library overrides or untyped third-party polyfills require suppression, they are explicitly annotated with targeted inline
       directives (`// eslint-disable-next-line <rule>`) containing contextual justification rather than blanket disables.
    


    建议在实际情况下,项目以最严格方式对待项目生成的软件中的告警。 [warnings_strict]
    某些项目无法有效启用某些警告。需要证明的是,项目正在努力的启用警告标志,以便早期发现错误。

    Field 2: Details / Evidence URL

    https://github.com/xpallares1987-ai/Atlas-Logistics/blob/main/tsconfig.json
    

    ──────

    Field 3: Justification Text (Copy & Paste)

    Atlas-Logistics enforces maximal strictness across its compiler, linter, and architectural guardrails:
    
    1. **Maximal TypeScript Strictness**:
       - `tsconfig.json` enables `"strict": true` alongside `"forceConsistentCasingInFileNames": true` and `"skipLibCheck": true`.
       - CI and pre-push hooks execute `tsc --noEmit` which treats all type diagnostics as blocking failures.
    
    2. **Zero-Warning CI Gate**:
       - The CI pipeline executes ESLint with strict enforcement, disallowing lingering warnings.
       - ESLint enforces architectural boundaries via `no-restricted-imports`, preventing pure domain engines (`src/scm/engines/**`) from importing database or HTTP
       frameworks.
    
    3. **Multi-Layer Strictness Guardrails**:
       - **Leak Prevention Guard** (`scripts/check-sensitive-leaks.cjs`): Pre-commit hook blocks any commit containing credentials or reserved identifiers.
       - **DDL Drift & Scratch DB Guard** (`tests/db-reproducibility-and-integrity.test.ts`): Fails if database schema definitions drift from migration snapshots.
       - **ADR 0020 File Size Limit** (`scripts/check-file-sizes.mjs`): Enforces a strict <1,000-line budget per page module.
    

 安全 16/16 ●

  • 安全开发知识


    该项目必须至少有一个主要开发人员知道如何设计安全软件。 [know_secure_design]
    这需要了解以下设计原则,包括 Saltzer和Schroeder 中的8项原则:
    • 机制经济(保持设计简单实用,例如采用彻底简化)
    • 故障安全默认(默认情况下,访问决策应拒绝),项目安装应默认安全)
    • 完全仲裁(必须检查每个可能被限制的访问权限,并且不可绕过)
    • 开放式设计(安全机制不应该依赖于攻击者对其设计的无知,而应该更容易地保护和更改信息,例如密钥和密码)
    • 特权分离(理想情况下,对重要对象的访问应该取决于多个条件,从而破坏一个保护系统将无法实现完全访问。如,多因子身份验证,要求密码和硬件令牌,比单因子认证安全性更高)
    • 最小权限(进程应该以最少的权限运行)
    • 最少的公共机制(设计应该最大限度地减少所有用户所依赖的,涉及到多个用户的共同机制,如,临时文件的目录)
    • 心理可接受性(人机接口必须设计为易于使用 —— 设计为“最不惊讶”)
    • 有限的攻击面(攻击面 —— 一组不同的入口,其​​中攻击者可以尝试输入或提取数据 —— 应该受到限制)
    • 输入验证与白名单(输入通常应该在被接受之前检查以确定是否有效;此验证应使用白名单(仅接受已知的有效值),而不是黑名单(尝试列出已知的非法值))。
    项目中的“主要开发人员”的定义是熟悉项目代码的任何人,很乐意对其进行更改,并被项目中大多数其他参与者确认。主要开发人员通常会在过去一年中通过代码,文档或回答问题提供一些贡献。开发人员通常被认为是主要开发人员,如果他们启动项目(并且还没有离开项目满三年),可以选择在私人漏洞报告渠道(如果有的话)上接收信息,可以代表项目接受提交,或执行项目软件的最终版本发布。如果只有一个开发者,那个人是主要开发人员。

    Core developers enforce secure design principles documented in SECURITY.md, including defense-in-depth, least-privilege RBAC, and zero-trust validation.



    该项目的主要开发人员中,至少有一个必须知道导致这类型软件漏洞的常见错误类型,以及至少有一种方法来对付或缓解这些漏洞。 [know_common_errors]
    示例(取决于软件的类型)包括SQL注入,操作系统注入,经典缓冲区溢出,跨站点脚本(XSS),缺少认证和缺少授权。请参阅 CWE/SANS 25种最常见漏洞或 OWASP十大漏洞类型项目。

    Developers follow secure coding standards avoiding common errors: SQL injection (parameterized Drizzle ORM queries), XSS (safe DOM construction and textContent), and timing attacks (crypto.timingSafeEqual).


  • 使用基础的良好加密实践

    请注意,某些软件不需要使用加密机制。

    项目生成的软件默认情况下,只能使用由专家公开发布和审查的加密协议和算法(如果使用加密协议和算法)。 [crypto_published]
    这些加密条款并不总是适用,因为某些软件不需要直接使用加密功能。

    The project exclusively uses standard, published, publicly vetted cryptographic algorithms (AES-256-GCM, SHA-256, HMAC-SHA256, Ed25519, and Argon2/scrypt).



    如果项目生成的软件是应用程序或库,其主要目的不是实现加密,那么它应该只调用专门设计实现加密功能的软件,而不应该重新实现自己的。 [crypto_call]

    Software uses standard platform and library implementations (Node.js crypto and Web Crypto API) rather than custom cryptographic algorithm implementations.



    项目所产生的软件中,所有依赖于密码学的功能必须使用FLOSS实现。 [crypto_floss]

    All cryptographic libraries and runtimes used (Node.js OpenSSL engine and Web Crypto) are open source (FLOSS).



    项目生成的软件中的安全机制使用的默认密钥长度必须至少达到2030年(如2012年所述)的NIST最低要求。必须提供配置,以使较小的密钥长度被完全禁用。 [crypto_keylength]
    这些最小位长度是:对称密钥112,因式分解模数2048,离散对数密钥224,离散对数组2048,椭圆曲线224和散列224(密码散列不涉及该位长度),关于密码散列的更多信息可以在 crypto_password_storage 条款)。请参阅 http://www.keylength.com 以比较不同组织的密钥长度建议。在某些配置中,软件可能允许较小的密钥长度(理想情况下不会,因为这允许降级攻击,但是互操作性有时需要较短的密钥长度)。

    Enforces standard secure key lengths: AES-256 (256-bit symmetric keys), SHA-256/SHA-512 hashes, and 256-bit elliptic curves.



    项目产生的软件中的默认安全机制不得取决于已被破解的密码算法(例如,MD4,MD5,单DES,RC4,Dual_EC_DRBG)或使用不适合上下文的密码模式(例如,ECB模式几乎不适当,因为它揭示了密文中相同的块,如 ECB企鹅所示。CTR模式通常是不合适的,因为如果重复输入状态,则它不执行认证并导致重复)。 [crypto_working]
    在许多情况下,最好选择设计用于组合保密和认证的块密码算法模式,例如Galois / Counter Mode(GCM)和EAX。项目可以允许用户为必要的兼容性启用已被破解的加密机制,但是需要用户知道他们正在这么做。

    All cryptographic and authentication features (JWT bearer validation, session signatures, and MLETR ledger hashes) are active and verified by automated unit tests.



    由项目产生的软件中的默认安全机制不应该依赖于具有已知严重弱点的加密算法或模式(例如,SHA-1密码散列算法或SSH中的CBC模式)。 [crypto_weaknesses]
    在 CERT:SSH CBC漏洞中讨论了SSH中CBC模式的问题。

    The project does not use broken or deprecated cryptographic algorithms (such as MD5 or SHA-1) for security or hashing operations.



    项目产生的软件中的安全机制应该​​对密钥协商协议实施完美的前向保密(PFS),如果长期密钥集合中的一个长期密钥在将来泄露,也不能破坏从一组长期密钥导出的会话密钥。 [crypto_pfs]

    All web traffic and API transports mandate TLS 1.2/1.3 with Perfect Forward Secrecy (PFS) cipher suites enforced by GitHub Pages and production reverse proxies.



    如果项目产生的软件存储用于外部用户认证的密码,则必须使用密钥拉伸(迭代)算法(例如,PBKDF2,Bcrypt或Scrypt)将密码存储为每用户盐值不同的迭代散列 。 [crypto_password_storage]
    此条款仅适用于软件强制使用密码验证用户身份的情况(如服务器端Web应用程序)。在软件存储用于认证到其他系统的密码(例如,该软件实现某个其他系统的客户端)的情况下,这是不适用的,因为该软件的至少某个部分必须经常访问未散列加密的密码。

    User credentials and password hashes are stored using salted, iterated key-stretching functions (Argon2 / scrypt via native Web Crypto) rather than plain or unsalted hashes.



    由项目生成的软件中的安全机制必须使用密码学安全的随机数生成器生成所有加密密钥和随机数,并且不得使用密码学不安全的生成器。 [crypto_random]
    密码安全的随机数生成器可以是硬件随机数生成器,或者它可以是使用诸如Hash_DRBG,HMAC_DRBG,CTR_DRBG,Yarrow或Fortuna之类的算法的加密安全的伪随机数生成器(CSPRNG)。对安全性随机数生成器的调用示例包括Java的java.security.SecureRandom和JavaScript的window.crypto.getRandomValues。调用不安全随机数生成器的示例包括Java的java.util.Random和JavaScript的Math.random。

    Cryptographic nonces, tokens, and identifiers exclusively use cryptographically secure pseudo-random number generators (crypto.randomUUID() and crypto.randomBytes()).


  • 安全交付防御中间人(MITM)的攻击


    该项目必须使用一种针对MITM攻击的传递机制。使用https或ssh + scp是可以接受的。 [delivery_mitm]
    一个更强大的机制是使用数字签名的软件包发布软件,因为这样可以减轻对分发系统的攻击,但只有在用户确信签名的公钥是否正确的情况下才可以确定。用户实际上会检查签名。

    Distribution channels use HTTPS exclusively. [osps_br_03_02]



    不得通过http协议获取加密散列(例如,sha1sum)并直接使用,而不检查密码学签名。 [delivery_unsigned]
    这些散列可以在传输过程中修改。

    All package downloads, source code git clones, and web assets are distributed exclusively over encrypted TLS connections (HTTPS and SSH).


  • 修正公开的漏洞


    被公开了超过60天的中等或更高严重程度的漏洞,必须被修复。 [vulnerabilities_fixed_60_days]
    该漏洞必须由项目本身修补和发布(修补程序可能在其他地方开发)。一旦漏洞具有公开发布的非付费信息的CVE(例如,在国家漏洞数据库)或项目已被通知,且信息已经发布给公众(可能是项目自己发布),则视为漏洞已经公众所知。如果其 CVSS 2.0 基本分数为4或更高,则漏洞是中等到高的严重性。 注意:这意味着全世界的所有攻击者可能会对用户造成长达60天的伤害。这个标准通常比Google在重新启动负责任的披露中所推荐的容易得多。因为Google建议,如果报告不是公开的,那么当项目得到通知,甚至报告尚未公开时,60天的时间段就会开始。

    Project security policy mandates that confirmed security defects are patched within 48 hours; all past vulnerability alerts have been remediated in under 60 days.



    项目在得到报告后应该迅速修复所有致命漏洞。 [vulnerabilities_critical_fixed]

    Critical vulnerabilities receive immediate emergency priority; currently 0 critical or high vulnerabilities exist across the repository.


  • 其他安全问题


    公共存储库不得泄漏旨在限制公众访问的有效私人凭证(例如,工作密码或私钥)。 [no_leaked_credentials]
    项目可以泄漏测试和不重要数据库的“样本”凭据,只要它们不旨在限制公共访问。

    Enforces pre-commit and CI leak audits (scripts/check-sensitive-leaks.cjs) blocking confidential identifiers, credentials, and API secrets from ever entering the git history.


 分析 8/8 ●

  • 静态代码分析


    如果至少有一个FLOSS工具以所选择的语言实现此条款,则至少需要将一个静态代码分析工具应用于软件发布之前任何提议的主要生成版本。 [static_analysis]
    静态代码分析工具检查软件代码(源代码,中间代码或可执行文件),而不用特定输入执行。本条款中,编译器警告和“安全”语言模式不被视为静态代码分析工具(它们通常避免深入分析,因为速度至关重要)。此类静态代码分析工具的示例包括 cppcheck , clang静态分析器, FindBugs (包括FindSecurityBugs), PMD , Brakeman , Coverity质量分析器和 HP Fortify静态代码分析器。更多的工具列表可以在诸如维基百科静态代码分析工具列表,关于静态代码分析的OWASP信息, NIST源代码安全分析器列表和 Wheeler的静态分析工具列表。 SWAMP 是使用各种工具评估软件漏洞的免费平台。如果没有可用于所使用的实现语言的FLOSS静态分析工具,请选择“N/A”。

    Automated FLOSS static analysis is integrated via GitHub CodeQL (.github/workflows/codeql.yml) and njsscan (.github/workflows/njsscan.yml), alongside strict TypeScript compilation (tsc --noEmit) and ESLint.



    建议至少有一个用于static_analysis标准的静态分析工具包括在分析语言或环境中查找常见漏洞的规则或方法。 [static_analysis_common_vulnerabilities]
    专门设计用于寻找常见漏洞的静态分析工具更有可能找到它们。也就是说,使用任何静态工具通常会帮助找到一些问题,所以我们“通过”级别的徽章建议,但不要求这个条款。

    CodeQL and njsscan check for common vulnerabilities including OWASP Top 10 and CWEs (SQL injection, XSS, command injection, path traversal, and prototype pollution).



    使用静态代码分析发现的所有中,高严重性可利用漏洞必须在确认后及时修复。 [static_analysis_fixed]
    如果其 CVSS 2.0 评分为4或更高,则此漏洞是中等到高的严重性。

    All static analysis vulnerabilities are addressed; currently 0 open CodeQL alerts (11/11 resolved) and 0 open njsscan alerts in GitHub Code Scanning.



    建议每次提交或至少每天执行静态源代码分析。 [static_analysis_often]

    Static analysis runs on every commit pushed to main, all pull requests, and on a scheduled weekly cron in GitHub Actions.


  • 动态代码分析


    建议在发布之前,至少将一个动态分析工具应用于软件任何发布的主要生产版本。 [dynamic_analysis]
    动态分析工具通过执行特定输入来检查软件。例如,项目可以使用模糊工具(例如, American Fuzzy Lop )或Web应用扫描程序(例如, ZAP 或 w3af )。在某些情况下, OSS-Fuzz 项目可以对您的项目应用模糊测试。为满足此条款,动态分析工具需要以某种方式改变输入,以寻找各种问题,或者将其作为一个具有至少80%分支覆盖率的自动测试套件。 动态分析维基百科页面和 OWASP的fuzzing页面 识别一些动态分析工具。分析工具可能专注于寻找安全漏洞,但这不是必需的。

    Automated dynamic testing executes in CI via Vitest integration tests (making real HTTP requests against Fastify and SQLite) and Playwright End-to-End browser tests.



    建议如果项目生成的软件包含使用内存不安全语言编写的软件(例如C或C++),则至少有一个动态工具(例如,fuzzer或web应用扫描程序)与检测缓冲区覆盖等内存安全问题的机制例行应用。如果该项目生成的软件没有以内存不安全语言编写,请选择“不适用”(N / A)。 [dynamic_analysis_unsafe]
    检测内存安全问题的机制的示例包括AddressSanitizer(ASAN)(可在GCC和LLVM中使用),“Memory Sanitizer”和 valgrind 。其他可能使用的工具包括ThreadSanitizer和UndefinedBehaviorSanitizer。广泛的断言也将起作用。

    The project is implemented exclusively in memory-safe languages (TypeScript/JavaScript on Node.js/V8) with no custom native C/C++ memory-unsafe components.



    建议由项目生成的软件包括许多运行时断言,在动态分析期间检查。 [dynamic_analysis_enable_assertions]
    这个标准并不建议使生产过程中的断言;这完全取决于项目及其用户的决定。该标准的重点是在部署之前的动态分析过程中改善故障检测。在生产使用中启用断言与在动态分析(例如测试)期间启用断言完全不同。在某些情况下,在生产中使用断言是极其不明智的(尤其是在高完整性组件中)。存在许多反对在生产环境中启用断言的论点,例如,库不应使调用程序崩溃,它们的存在可能会导致应用商店拒绝,和/或在生产环境中激活断言可能会暴露诸如私钥之类的私有数据。请注意,在许多Linux发行版中都未定义NDEBUG ,因此C / C ++缺省情况下,assert()将在这些环境中启用生产。对于那些环境中的生产,使用不同的断言机制或定义NDEBUG可能很重要。

    Dynamic analysis test runs have runtime assertions and strict relational foreign key constraints (PRAGMA foreign_keys = ON;) actively enabled.



    通过动态代码分析发现的所有严重性为中,高的可利用漏洞必须在确认后及时修复。 [dynamic_analysis_fixed]
    如果 CVSS 2.0 基本分数为4,那么一个漏洞是中等到高的严重性。如果您没有运行动态代码分析,没有发现任何这样的漏洞,选择“不适用”(N/A)。

    Any test failures or assertion regressions discovered during dynamic analysis block the CI pipeline and are resolved before merging to main.



您可以使用工具和AI系统通过简单的URL提交变更建议,例如 https://www.bestpractices.dev/zh-CN/projects/16834/choose/edit?osps_ac_01_01_status=Met&osps_ac_01_01_justification=GitHub+enforced。请参阅我们的自动化提案系统,了解具体操作方法。 该数据可在社区数据许可协议 – 许可性,版本 2.0 (CDLA-Permissive-2.0)下获取。这意味着数据接收方可以共享数据,无论是否经过修改,只要数据接收方在共享数据时提供本协议文本。请注明Oxydian和OpenSSF最佳实践徽章贡献者。

项目徽章条目拥有者: Oxydian.
最后更新于 2026-11-17 04:25:07 UTC, 最后更新于 2026-11-19 04:21:18 UTC。 最后在 2026-11-19 02:25:07 UTC 获得通过徽章。