GenevaERS

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 4181 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

    GenevaERS solves problem of efficiently reporting on large volumes of transactional data. It is a set of software components with previously patented technology embedded, and it may be customized for use with new or existing data extraction and reporting applications.

  • Prerequisites


    Not enough for a badge.

    The project MUST achieve a silver level badge. [achieve_silver]

  • Project oversight


    Unknown required information, not enough for a badge.

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

    Warning: URL required, but no URL found.


    Unknown required information, not enough for a badge.

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

    Warning: URL required, but no URL found.


  • 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]

    Warning: Requires lengthier justification.


  • Public version-controlled source repository


    Enough for a badge!

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

    we are using git Repository on GitHub, which uses git. git is distributed.


    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]

    Most items are too advanced for someone without project or mainframe knowledge. When mainframe is available, one task could be to follow documentation and run the demo. other possibilities are helping to convert genevaers to jekyll, or documentation feedback. will need to break down when work gets far enough along.


    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]

    This project abides by the Open Mainframe Project's guidance to use 2FA for repositories. The guidance is documented in the Open Mainframe Project's contribution guidelines https://github.com/openmainframeproject/tac/blob/main/process/contribution_guidelines.md.


    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]

    This project abides by the Open Mainframe Project's guidance to use 2FA for repositories. The guidance is documented in the Open Mainframe Project's contribution guidelines https://github.com/openmainframeproject/tac/blob/main/process/contribution_guidelines.md.


  • 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]

    Will be invoked by GRADLE and written in JAVA

    Warning: URL required, but no URL found.


    Unknown required information, not 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]

    will be followed

    Warning: URL required, but no URL found.


    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]

    Warning: Requires lengthier justification.


    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]

    Warning: Requires lengthier justification.


  • Use basic good cryptographic practices

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

    Enough for a badge!

    The software produced by the project MUST 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]

    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]

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


    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]

    Found all required security hardening headers. // X-Content-Type-Options was not set to "nosniff".


  • Other security issues


    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]

    Unknown required information, not 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]

    Warning: Requires lengthier justification.


  • Dynamic code analysis


    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]

    Will deploy GitLab CI/CD,


    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]

    As most of the product runs on z/OS this is not feasible. The Java portion on the Eclipse IDE maybe possible



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 bobmcc9 and the OpenSSF Best Practices badge contributors.

Project badge entry owned by: bobmcc9.
Entry created on 2020-08-03 05:04:09 UTC, last updated on 2025-03-01 22:22:56 UTC. Last achieved passing badge on 2021-02-26 00:11:54 UTC.

Back