Automation-repetitive-task-software

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 8239 is gold Here is how to embed it:

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

        

 Basics 13/13

  • Identification

    Tremendous automation repetitive task Sofware with the motive of contributing to what makes your day to day activities much easier and accessible for you at your work place.

    What programming language(s) are used to implement the project?
  • Basic project website content


    The project website MUST succinctly describe what the software does (what problem does it solve?). [description_good]

    The project website MUST provide information on how to: obtain, provide feedback (as bug reports or enhancements), and contribute to the software. [interact]

    La información sobre cómo contribuir DEBE explicar el proceso de contribución (por ejemplo, ¿se utilizan "pull requests" en el proyecto?) (URL required) [contribution]

    Projects on GitHub by default use issues and pull requests, as encouraged by documentation such as https://guides.github.com/activities/contributing-to-open-source/.



    The information on how to contribute SHOULD include the requirements for acceptable contributions (e.g., a reference to any required coding standard). (URL required) [contribution_requirements]

    Firstly, I was able to solve the problem on the changing default personal email address and that's how I was able to link to my stack workplace for my organization for easy assistance on how I fix all the issues and work with daily emails on that too. Most importantly. I initiated a public template which will make it easier and more comfortable to use and even if the user doesn't understand how the software was build. with the public template on my repository, it's 100% ready to be used positively! Although, specific users or contributors, Members, billing managers, and outside collaborators who do not have two-factor authentication enabled for their personal account will be removed from my organization and will receive an email notifying them about the change. I made a reference on this on this link: https://github.com/KIDI-S-TECH/Automation-repetitive-task-software


  • FLOSS license

    What license(s) is the project released under?



    The software produced by the project MUST be released as FLOSS. [floss_license]

    The MIT license is approved by the Open Source Initiative (OSI).



    It is SUGGESTED that any required license(s) for the software produced by the project be approved by the Open Source Initiative (OSI). [floss_license_osi]

    The MIT license is approved by the Open Source Initiative (OSI).



    The project MUST post the license(s) of its results in a standard location in their source repository. (URL required) [license_location]
  • Documentation


    The project MUST provide basic documentation for the software produced by the project. [documentation_basics]

    // No appropriate folder found for documentation basics.



    The project MUST provide reference documentation that describes the external interface (both input and output) of the software produced by the project. [documentation_interface]

  • Other


    The project sites (website, repository, and download URLs) MUST support HTTPS using TLS. [sites_https]

    Given only https: URLs.



    The project MUST have one or more mechanisms for discussion (including proposed changes and issues) that are searchable, allow messages and topics to be addressed by URL, enable new people to participate in some of the discussions, and do not require client-side installation of proprietary software. [discussion]

    GitHub supports discussions on issues and pull requests.



    The project SHOULD provide documentation in English and be able to accept bug reports and comments about code in English. [english]


    The project MUST be maintained. [maintained]

    sincerely speaking, I never knew what I was doing but I see myself proactively maintaining and protecting my software from vulnerabilities, fixing bugs issues, workflows and packages was not an easy task. but I was able make it easier for me when I started reading up on the GitHub Advanced Security. those tools are wonderfully deployed for Advanced security on GitHub. for instance, I was able to make use of the vulnerability scanning tool, secret scanning tool and the dependency graph which is how I got notifications whenever my tool detect any risk on any of my repo. also, see my progress and weakness on the dependency graph. though it wasn't an easier one, but I'm delighted that the hours that I spent solving and maintaining my repository really worth it.



(Advanced) What other users have additional rights to edit this badge entry? Currently: []



In addition to that, from my own Perceptive as an aspiring entry-level cybersecurity position, I think this software named: Automation-repetitive-task-software should be a better way and motion to look into and reconsider when handling the security protocols of large-scale corporation or small-scale corporation and organization in cybersecurity. I'm so happy sharing such a tremendous work with the community.

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


    El proyecto DEBE tener un repositorio público para el control de versiones de código fuente que sea legible públicamente y tenga URL. [repo_public]

    Repository on GitHub, which provides public git repositories with URLs.



    El repositorio fuente del proyecto DEBE rastrear qué cambios se realizaron, quién realizó los cambios y cuándo se realizaron los cambios. [repo_track]

    Repository on GitHub, which uses git. git can track the changes, who made them, and when they were made.



    To enable collaborative review, the project's source repository MUST include interim versions for review between releases; it MUST NOT include only final releases. [repo_interim]


    It is SUGGESTED that common distributed version control software be used (e.g., git) for the project's source repository. [repo_distributed]

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


  • Numeración única de versión


    The project results MUST have a unique version identifier for each release intended to be used by users. [version_unique]

    I used v2.3.4 for my release and it's meant for the purpose of production. and it can be used by everybody with the unique the version identifier stated below which is my URL for the tag release link which can be used by users as a guild to set up theirs properly. https://github.com/KIDI-S-TECH/Automation-repetitive-task-software/tree/v2.3.4



    It is SUGGESTED that the Semantic Versioning (SemVer) or Calendar Versioning (CalVer) version numbering format be used for releases. It is SUGGESTED that those who use CalVer include a micro level value. [version_semver]


    It is SUGGESTED that projects identify each release within their version control system. For example, it is SUGGESTED that those using git identify each release using git tags. [version_tags]
  • Notas de lanzamiento


    The project MUST provide, in each release, release notes that are a human-readable summary of major changes in that release to help users determine if they should upgrade and what the upgrade impact will be. The release notes MUST NOT be the raw output of a version control log (e.g., the "git log" command results are not release notes). Projects whose results are not intended for reuse in multiple locations (such as the software for a single website or service) AND employ continuous delivery MAY select "N/A". (URL required) [release_notes]

    The release notes MUST identify every publicly known run-time vulnerability fixed in this release that already had a CVE assignment or similar when the release was created. This criterion may be marked as not applicable (N/A) if users typically cannot practically update the software themselves (e.g., as is often true for kernel updates). This criterion applies only to the project results, not to its dependencies. If there are no release notes or there have been no publicly known vulnerabilities, choose N/A. [release_notes_vulns]

    N/A


  • Bug-reporting process


    The project MUST provide a process for users to submit bug reports (e.g., using an issue tracker or a mailing list). (URL required) [report_process]

    The project SHOULD use an issue tracker for tracking individual issues. [report_tracker]

    with the help of the bot on stack. it helps me on tracking issues detected on my organization and project. also, I gave some of organization members role to open an issue pull request which will actually trigger or detect an alert on my stack workplace for easy and fast responses. the link below will explain more. https://join.slack.com/share/enQtNjQwNTkxMzU2NDYwOS0zZmViMWFhYmQ2OTAzMjgzYzhkZTBjNTM1MjYzNTQ2N2Y2ZGUwNzUyZjYwNzBlNzYwMGIwMTVlOTc3YTJhNDhl



    The project MUST acknowledge a majority of bug reports submitted in the last 2-12 months (inclusive); the response need not include a fix. [report_responses]

    Currently I'm using Checkly for my bug reports and it's doing a good job on that too. it was reporting and solving the issues on my other projects before now.



    The project SHOULD respond to a majority (>50%) of enhancement requests in the last 2-12 months (inclusive). [enhancement_responses]


    El proyecto DEBE tener un archivo públicamente disponible para informes y respuestas para búsquedas posteriores. (URL required) [report_archive]
  • Proceso de informe de vulnerabilidad


    The project MUST publish the process for reporting vulnerabilities on the project site. (URL required) [vulnerability_report_process]

    If private vulnerability reports are supported, the project MUST include how to send the information in a way that is kept private. (URL required) [vulnerability_report_private]

    The project's initial response time for any vulnerability report received in the last 6 months MUST be less than or equal to 14 days. [vulnerability_report_response]

  • Working build system


    Si el software generado por el proyecto requiere ser construido para su uso, el proyecto DEBE proporcionar un sistema de compilación que pueda satisfactoriamente reconstruir automáticamente el software a partir del código fuente. [build]

    100% I've created a public template for project. however, any user who have access to it can easily rebuild the software automatically from the source code. On that note, on my backend where I deployed my software to Cloud from the source code merged with the rapid increase on the cloud security now. on my end, is a very good way to build a tremendous solid and running system that will keep iterating without breaking out with good maintainers.



    Se SUGIERE que se utilicen herramientas comunes para construir el software. [build_common_tools]


    El proyecto DEBERÍA ser construible usando solo herramientas FLOSS. [build_floss_tools]

  • Automated test suite


    The project MUST use at least one automated test suite that is publicly released as FLOSS (this test suite may be maintained as a separate FLOSS project). The project MUST clearly show or document how to run the test suite(s) (e.g., via a continuous integration (CI) script or via documentation in files such as BUILD.md, README.md, or CONTRIBUTING.md). [test]


    Un conjunto de pruebas DEBERÍA ser invocable de forma estándar para ese lenguaje. [test_invocation]

    An html file was used to test the code in a way it pass the automation test and then run the code to test or confirmation. It passed the test and was awarded an html passing badge URL: https://github.com/KIDI-STECH/demo-repository



    It is SUGGESTED that the test suite cover most (or ideally all) the code branches, input fields, and functionality. [test_most]

    well, I created a README.md on my project which explains my project step by step. and how the functionalities were implemented and embedded on my software with link below will display a clear review of project. https://github.com/KIDI-S-TECH/Automation-repetitive-task-software



    It is SUGGESTED that the project implement continuous integration (where new or changed code is frequently integrated into a central code repository and automated tests are run on the result). [test_continuous_integration]

    yes, it does. the link below is a great one to jump on in reference to how continuous integration the software can run when codes are changed frequently. though it depends on what was removed and replaced on my software. for more details on how to use, the link below will redirect to my README.md for proper review. https://github.com/KIDI-S-TECH/demo-repository


  • New functionality testing


    The project MUST have a general policy (formal or not) that as major new functionality is added to the software produced by the project, tests of that functionality should be added to an automated test suite. [test_policy]

    The project MUST have evidence that the test_policy for adding tests has been adhered to in the most recent major changes to the software produced by the project. [tests_are_added]

    It is SUGGESTED that this policy on adding tests (see test_policy) be documented in the instructions for change proposals. [tests_documented_added]

    This can be seen on the feature.md file on GitHub website of the project. The file helps users to understand and contribute to new features or functionality on the project. URL: https://github.com/KIDI-S-TECH/Automation-repetitive-task-software/blob/main/.github/ISSUE_TEMPLATE/feature_request.md?plain=1


  • Banderas de advertencia


    The project MUST enable one or more compiler warning flags, a "safe" language mode, or use a separate "linter" tool to look for code quality errors or common simple mistakes, if there is at least one FLOSS tool that can implement this criterion in the selected language. [warnings]


    El proyecto DEBE abordar las advertencias. [warnings_fixed]


    It is SUGGESTED that projects be maximally strict with warnings in the software produced by the project, where practical. [warnings_strict]
  • Conocimiento de desarrollo seguro


    The project MUST have at least one primary developer who knows how to design secure software. (See ‘details’ for the exact requirements.) [know_secure_design]

    100% the software development or my project has a developer who knows how to design secure software. One of my projects that has a top notch design software is Free dictionary API with JavaScript: which explains so much on how to design, secure and manage a good API project. URL: https://github.com/KidiIT/Free--Dictionary-API



    At least one of the project's primary developers MUST know of common kinds of errors that lead to vulnerabilities in this kind of software, as well as at least one method to counter or mitigate each of them. [know_common_errors]

    well, I can comfortably design or build a responsive website or software with HTML, CSS and JavaScript. and thank you so very much for the heads up. I'll explore more on the link. these are some of my projects with full frontend. thanks once again. https://github.com/KidiIT/Free--Dictionary-API https://github.com/KidiIT/Customer-interactive-score-card-rating https://github.com/KidiIT/-Password-generator-software-with-Javascript


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

    The software produced by the project MUST use, by default, only cryptographic protocols and algorithms that are publicly published and reviewed by experts (if cryptographic protocols and algorithms are used). [crypto_published]


    Si el software producido por el proyecto es una aplicación o una librería, y su propósito principal no es implementar criptografía, entonces DEBE SOLAMENTE invocar un software específicamente diseñado para implementar funciones criptográficas; NO DEBERÍA volver a implementar el suyo. [crypto_call]


    All functionality in the software produced by the project that depends on cryptography MUST be implementable using FLOSS. [crypto_floss]


    The security mechanisms within the software produced by the project MUST use default keylengths that at least meet the NIST minimum requirements through the year 2030 (as stated in 2012). It MUST be possible to configure the software so that smaller keylengths are completely disabled. [crypto_keylength]


    The default security mechanisms within the software produced by the project MUST NOT depend on broken cryptographic algorithms (e.g., MD4, MD5, single DES, RC4, Dual_EC_DRBG), or use cipher modes that are inappropriate to the context, unless they are necessary to implement an interoperable protocol (where the protocol implemented is the most recent version of that standard broadly supported by the network ecosystem, that ecosystem requires the use of such an algorithm or mode, and that ecosystem does not offer any more secure alternative). The documentation MUST describe any relevant security risks and any known mitigations if these broken algorithms or modes are necessary for an interoperable protocol. [crypto_working]


    The default security mechanisms within the software produced by the project SHOULD NOT depend on cryptographic algorithms or modes with known serious weaknesses (e.g., the SHA-1 cryptographic hash algorithm or the CBC mode in SSH). [crypto_weaknesses]

    This isn’t applicable on my project because cryptographic algorithms or modes with know serious weaknesses are not available or applicable on the project itself.



    The security mechanisms within the software produced by the project SHOULD implement perfect forward secrecy for key agreement protocols so a session key derived from a set of long-term keys cannot be compromised if one of the long-term keys is compromised in the future. [crypto_pfs]


    If the software produced by the project causes the storing of passwords for authentication of external users, the passwords MUST be stored as iterated hashes with a per-user salt by using a key stretching (iterated) algorithm (e.g., Argon2id, Bcrypt, Scrypt, or PBKDF2). See also OWASP Password Storage Cheat Sheet. [crypto_password_storage]


    The security mechanisms within the software produced by the project MUST generate all cryptographic keys and nonces using a cryptographically secure random number generator, and MUST NOT do so using generators that are cryptographically insecure. [crypto_random]

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


    The project MUST use a delivery mechanism that counters MITM attacks. Using https or ssh+scp is acceptable. [delivery_mitm]


    A cryptographic hash (e.g., a sha1sum) MUST NOT be retrieved over http and used without checking for a cryptographic signature. [delivery_unsigned]

  • Vulnerabilidades públicamente conocidas corregidas


    There MUST be no unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days. [vulnerabilities_fixed_60_days]


    Projects SHOULD fix all critical vulnerabilities rapidly after they are reported. [vulnerabilities_critical_fixed]

  • Otros problemas de seguridad


    The public repositories MUST NOT leak a valid private credential (e.g., a working password or private key) that is intended to limit public access. [no_leaked_credentials]

    I enable a strict setting to keep everything on repositories and project private.


  • Análisis estático de código


    At least one static code analysis tool (beyond compiler warnings and "safe" language modes) MUST be applied to any proposed major production release of the software before its release, if there is at least one FLOSS tool that implements this criterion in the selected language. [static_analysis]

    they are used to support continuous integration and deployment and maintain with the aim of mitigating risks, threats and vulnerabilities.



    It is SUGGESTED that at least one of the static analysis tools used for the static_analysis criterion include rules or approaches to look for common vulnerabilities in the analyzed language or environment. [static_analysis_common_vulnerabilities]

    Yes, I used a static analysis tool on my project which periodically check for any vulnerabilities on my project and in an analyzed language or environment. the CodeQL / Analyze (javascript-typescript) (dynamic). the GitHub Advanced security also help in a more productive way. URL: https://github.com/KIDI-S-TECH/Automation-repetitive-task-software/actions/runs/8928352421/job/24523743906



    All medium and higher severity exploitable vulnerabilities discovered with static code analysis MUST be fixed in a timely way after they are confirmed. [static_analysis_fixed]


    It is SUGGESTED that static source code analysis occur on every commit or at least daily. [static_analysis_often]

  • Dynamic code analysis


    It is SUGGESTED that at least one dynamic analysis tool be applied to any proposed major production release of the software before its release. [dynamic_analysis]

    The software uses codeQL analysis tool which helps to keep the software updated to its latest version. Also with the help of the dependabot.yml plugin that was configured on the project also helps to keep the project updated to its latest version and release. URL: https://github.com/KidiIT/Automation-repetitive-task-software/releases



    It is SUGGESTED that if the software produced by the project includes software written using a memory-unsafe language (e.g., C or C++), then at least one dynamic tool (e.g., a fuzzer or web application scanner) be routinely used in combination with a mechanism to detect memory safety problems such as buffer overwrites. If the project does not produce software written in a memory-unsafe language, choose "not applicable" (N/A). [dynamic_analysis_unsafe]

    this is not applicable on my project because it's not written using a memory-unsafe language.



    It is SUGGESTED that the project use a configuration for at least some dynamic analysis (such as testing or fuzzing) which enables many assertions. In many cases these assertions should not be enabled in production builds. [dynamic_analysis_enable_assertions]

    I configured a codeQL code analysis file and dependencies run that focus on every single Check run test on the project. After which it output the report with a debug terminal to debug the issue directly on the repository if the check failed.



    All medium and higher severity exploitable vulnerabilities discovered with dynamic code analysis MUST be fixed in a timely way after they are confirmed. [dynamic_analysis_fixed]


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 KIDI'S-TECH and the OpenSSF Best Practices badge contributors.

Project badge entry owned by: KIDI'S-TECH.
Entry created on 2023-12-25 23:03:33 UTC, last updated on 2024-05-31 18:18:13 UTC. Last achieved passing badge on 2024-05-02 15:25:30 UTC.

Back