zerodep.app

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.

If this is your project, please show your badge status on your project page! The badge status looks like this: Badge level for project 9225 is passing Here is how to embed it:

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

        

 Basics 0/5 ●

  • Identification

    A modern library of high quality, zero-dependency, fully typed, tree-shakeable utilities, parsers, data structure factories, converters and other capabilities to help in crafting quality Node.js/Bun and JavaScript/TypeScript applications quickly.

  • Prerrequisitos


    Not enough for a badge.

    El proyecto DEBE lograr una insignia de nivel plata. [achieve_silver]

  • Supervisión del proyecto


    Unknown required information, not enough for a badge.

    The project MUST have a "bus factor" of 2 or more. (URL required) [bus_factor]

    As this project is fully open source and hosted on GitHub, anybody so choosing is able to clone the project and continue development.


    Unknown required information, not enough for a badge.

    The project MUST have at least two unassociated significant contributors. (URL required) [contributors_unassociated]

  • Other


    Unknown required information, not enough for a badge.

    The project MUST include a license statement in each source file. This MAY be done by including the following inside a comment near the beginning of each file: SPDX-License-Identifier: [SPDX license expression for project]. [license_per_file]

  • Repositorio público para el control de versiones de código fuente


    Enough for a badge!

    The project's source repository MUST use a common distributed version control software (e.g., git or mercurial). [repo_distributed]

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


    Unknown required information, not enough for a badge.

    The project MUST clearly identify small tasks that can be performed by new or casual contributors. (URL required) [small_tasks]

    Unknown required information, not enough for a badge.

    The project MUST require two-factor authentication (2FA) for developers for changing a central repository or accessing sensitive data (such as private vulnerability reports). This 2FA mechanism MAY use mechanisms without cryptographic mechanisms such as SMS, though that is not recommended. [require_2FA]

    Unknown required information, not enough for a badge.

    The project's two-factor authentication (2FA) SHOULD use cryptographic mechanisms to prevent impersonation. Short Message Service (SMS) based 2FA, by itself, does NOT meet this criterion, since it is not encrypted. [secure_2FA]

  • Coding standards


    Unknown required information, not enough for a badge.

    The project MUST document its code review requirements, including how code review is conducted, what must be checked, and what is required to be acceptable. (URL required) [code_review_standards]

    Unknown required information, not enough for a badge.

    The project MUST have at least 50% of all proposed modifications reviewed before release by a person other than the author, to determine if it is a worthwhile modification and free of known issues which would argue against its inclusion [two_person_review]

  • Working build system


    Unknown required information, not enough for a badge.

    The project MUST have a reproducible build. If no building occurs (e.g., scripting languages where the source code is used directly instead of being compiled), select "not applicable" (N/A). (URL required) [build_reproducible]

  • Automated test suite


    Unknown required information, not enough for a badge.

    A test suite MUST be invocable in a standard way for that language. (URL required) [test_invocation]

    All tests are publicly available and are co-located with the source code. Test scripts, including determining code test coverage may be run via typical NPM scripts: - npm run test:all - npm run buld:all

    Warning: URL required, but no URL found.


    Enough for a badge!

    The project MUST implement continuous integration, where new or changed code is frequently integrated into a central code repository and automated tests are run on the result. (URL required) [test_continuous_integration]

    GitHub actions are also used in a CI/CD capacity that lints, tests and builds the software with each commit. - https://github.com/cdepage/zerodep/blob/main/.github/workflows/ci.yml


    Unknown required information, not enough for a badge.

    The project MUST have FLOSS automated test suite(s) that provide at least 90% statement coverage if there is at least one FLOSS tool that can measure this criterion in the selected language. [test_statement_coverage90]

    Unknown required information, not enough for a badge.

    The project MUST have FLOSS automated test suite(s) that provide at least 80% branch coverage if there is at least one FLOSS tool that can measure this criterion in the selected language. [test_branch_coverage80]

  • Use buenas prácticas criptográficas

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

    Enough for a badge!

    The software produced by the project MUST support secure protocols for all of its network communications, such as SSHv2 or later, TLS1.2 or later (HTTPS), IPsec, SFTP, and SNMPv3. Insecure protocols such as FTP, HTTP, telnet, SSLv3 or earlier, and SSHv1 MUST be disabled by default, and only enabled if the user specifically configures it. If the software produced by the project does not support network communications, select "not applicable" (N/A). [crypto_used_network]

    While this project does not provide any functionality nor relies upon any functionality requiring cryptography, it is available from multiple sources (e.g. NPM or GitHub) that enforce HTTPS requirements. The accounts at each location are also configured to require MFAs for all maintainers.


    Enough for a badge!

    The software produced by the project MUST, if it supports or uses TLS, support at least TLS version 1.2. Note that the predecessor of TLS was called SSL. If the software does not use TLS, select "not applicable" (N/A). [crypto_tls12]

    This project does not provide any functionality nor relies upon any functionality requiring cryptography.


  • Entrega garantizada contra ataques de hombre en el medio (MITM)


    Not enough for a badge.

    The project website, repository (if accessible via the web), and download site (if separate) MUST include key hardening headers with nonpermissive values. (URL required) [hardened_site]

    // X-Content-Type-Options was not set to "nosniff".


  • Otros problemas de seguridad


    Unknown required information, not enough for a badge.

    The project MUST have performed a security review within the last 5 years. This review MUST consider the security requirements and security boundary. [security_review]

    Enough for a badge!

    Hardening mechanisms MUST be used in the software produced by the project so that software defects are less likely to result in security vulnerabilities. (URL required) [hardening]

    The purpose of a lot of the JavaScript packages created by this project are intended to minimize attack surface areas by having no third-party dependencies. As this is publicly distributed by NPM, there is no need for browser-based hardening mechanisms such as CSP.


  • Dynamic code analysis


    Not enough for a badge.

    The project MUST apply at least one dynamic analysis tool to any proposed major production release of the software produced by the project before its release. [dynamic_analysis]

    This project has comprehensive unit testing that exercise the code against the full range of input types found within a TypeScript/JavaScript environment. Full details may be found within each test co-located with the source code: - https://github.com/cdepage/zerodep/tree/main/packages


    Enough for a badge!

    The project SHOULD include many run-time assertions in the software it produces and check those assertions during dynamic analysis. [dynamic_analysis_enable_assertions]

    This project has comprehensive unit testing that exercise the code against the full range of input types found within a TypeScript/JavaScript environment. Full details may be found within each test co-located with the source code: - https://github.com/cdepage/zerodep/tree/main/packages



This data is available under the Creative Commons Attribution version 3.0 or later license (CC-BY-3.0+). All are free to share and adapt the data, but must give appropriate credit. Please credit Chris dePage and the OpenSSF Best Practices badge contributors.

Project badge entry owned by: Chris dePage.
Entry created on 2024-07-20 16:07:08 UTC, last updated on 2024-07-21 00:02:23 UTC. Last achieved passing badge on 2024-07-20 20:30:07 UTC.

Back