BadgeApp

Identification

What is the human-readable name of the project?

Note that other projects may use the same name.

What is a brief description of the project?

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 is the URL for the project (as a whole)?

https://github.com/KIDI-S-TECH/Automation-repetitive-task-software.git

What is the URL for the version control repository (it may be the same as the project URL)?

https://github.com/KIDI-S-TECH/Automation-repetitive-task-software/releases/tag/v2.3.4

Prerrequisitos

Met

Unmet

The project MUST achieve a passing level badge. ^{[achieve_passing]}

Basic project website content

Met

Unmet

?

The information on how to contribute MUST 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

Supervisión del proyecto

Met

Unmet

?

The project SHOULD have a legal mechanism where all developers of non-trivial amounts of project software assert that they are legally authorized to make these contributions. The most common and easily-implemented approach for doing this is by using a Developer Certificate of Origin (DCO), where users add "signed-off-by" in their commits and the project links to the DCO website. However, this MAY be implemented as a Contributor License Agreement (CLA), or other legal mechanism. (URL required) ^[dco]

The DCO is the recommended mechanism because it's easy to implement, tracked in the source code, and git directly supports a "signed-off" feature using "commit -s". To be most effective it is best if the project documentation explains what "signed-off" means for that project. A CLA is a legal agreement that defines the terms under which intellectual works have been licensed to an organization or project. A contributor assignment agreement (CAA) is a legal agreement that transfers rights in an intellectual work to another party; projects are not required to have CAAs, since having CAA increases the risk that potential contributors will not contribute, especially if the receiver is a for-profit organization. The Apache Software Foundation CLAs (the individual contributor license and the corporate CLA) are examples of CLAs, for projects which determine that the risks of these kinds of CLAs to the project are less than their benefits.

That’s a very great question, my project met this criteria in two different ways, firstly, the signed off features that I implemented on my project which will display the signed off feature of any developer or contributor after making a contribution on my project. The url where you’ll see examples of my signed off features using commit on GitHub. URL: https://github.com/KIDI-S-TECH/Automation-repetitive-task-software/pull/1 The url below shows the commit that I made on a pull request that I successfully merged on my project. Secondly, I used the zenodo company to get my DOI which identified as a digital Object identification. That been said, The CAA agreement is on the website which developers, contributors and companies can go through to understand the terms and conditions of the project. URL: https://zenodo.org/records/10829824

Met

Unmet

?

The project MUST clearly define and document its project governance model (the way it makes decisions, including key roles). (URL required) ^[governance]

There needs to be some well-established documented way to make decisions and resolve disputes. In small projects, this may be as simple as "the project owner and lead makes all final decisions". There are various governance models, including benevolent dictator and formal meritocracy; for more details, see Governance models. Both centralized (e.g., single-maintainer) and decentralized (e.g., group maintainers) approaches have been successfully used in projects. The governance information does not need to document the possibility of creating a project fork, since that is always possible for FLOSS projects.

That’s a very good question, I made a software documentation on my project which clearly define and document its project governance model. URL below: https://github.com/KidiIT/.vscode#softwareproject-documentation

Met

Unmet

?

The project MUST adopt a code of conduct and post it in a standard location. (URL required) ^{[code_of_conduct]}

Projects may be able to improve the civility of their community and to set expectations about acceptable conduct by adopting a code of conduct. This can help avoid problems before they occur and make the project a more welcoming place to encourage contributions. This should focus only on behavior within the community/workplace of the project. Example codes of conduct are the Linux kernel code of conduct, the Contributor Covenant Code of Conduct, the Debian Code of Conduct, the Ubuntu Code of Conduct, the Fedora Code of Conduct, the GNOME Code Of Conduct, the KDE Community Code of Conduct, the Python Community Code of Conduct, The Ruby Community Conduct Guideline, and The Rust Code of Conduct.

Well, I followed the community standards to add a distinct code of conduct of my project and it was posted in a standard location. Please view the url below to confirm. URL: https://github.com/KIDI-S-TECH/Automation-repetitive-task-software?tab=coc-ov-file#

Met

Unmet

?

The project MUST clearly define and publicly document the key roles in the project and their responsibilities, including any tasks those roles must perform. It MUST be clear who has which role(s), though this might not be documented in the same way. (URL required) ^{[roles_responsibilities]}

The documentation for governance and roles and responsibilities may be in one place.

My project clearly define and publicly document the key roles in the project and their responsibilities. This aspect of this classification can be seen on my project documentation where all key roles and responsibilities was identified on my project. To tell users the right people to make use of my software and right business sector that it’ll perform better when used properly. URL: https://github.com/KidiIT/Automation-repetitive-task-software#

Met

Unmet

?

The project MUST be able to continue with minimal interruption if any one person dies, is incapacitated, or is otherwise unable or unwilling to continue support of the project. In particular, the project MUST be able to create and close issues, accept proposed changes, and release versions of software, within a week of confirmation of the loss of support from any one individual. This MAY be done by ensuring someone else has any necessary keys, passwords, and legal rights to continue the project. Individuals who run a FLOSS project MAY do this by providing keys in a lockbox and a will providing any needed legal rights (e.g., for DNS names). (URL required) ^{[access_continuity]}

My project met this requirements because it has the potential and ability to create and close issues, accept proposed changes and release versions of the software. Contributors can propose changes by opening a pull requests on the project url. If it’s accepted then any requests that met the changes will be amended immediately. As an individual who runs a FLOSS project under MIT license and users can see how this tremendous project perform such task can be seen on the URL below. Legal rights URL: https://github.com/KidiIT/Automation-repetitive-task-software/blob/main/LICENSE

Met

Unmet

?

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

A "bus factor" (aka "truck factor") is the minimum number of project members that have to suddenly disappear from a project ("hit by a bus") before the project stalls due to lack of knowledgeable or competent personnel. The truck-factor tool can estimate this for projects on GitHub. For more information, see Assessing the Bus Factor of Git Repositories by Cosentino et al.

Thank you for the opportunity to share the details about my work. However, I was able to acquire the Digital object identification badge through zenodo which makes all my research contributions and recognition attributed to me. The DOI provides a comprehensive bus factor where Bus factor was linked to my GitHub account through the zenodo website. URL: https://zenodo.org/records/10829824

Documentation

Met

Unmet

?

The project MUST have a documented roadmap that describes what the project intends to do and not do for at least the next year. (URL required) ^{[documentation_roadmap]}

The project might not achieve the roadmap, and that's fine; the purpose of the roadmap is to help potential users and contributors understand the intended direction of the project. It need not be detailed.

The document was written on my README.md and other standard location for collaborators URL: https://github.com/KIDI-S-TECH/Automation-repetitive-task-software#

Met

Unmet

N/A

?

The project MUST include documentation of the architecture (aka high-level design) of the software produced by the project. If the project does not produce software, select "not applicable" (N/A). (URL required) ^{[documentation_architecture]}

A software architecture explains a program's fundamental structures, i.e., the program's major components, the relationships among them, and the key properties of these components and relationships.

The documentation of the architecture which explains how the project produced high level design can we seen on the project README.md when the design documentation was published and released. URL; https://github.com/KidiIT/Automation-repetitive-task-software#

Met

Unmet

N/A

?

The project MUST document what the user can and cannot expect in terms of security from the software produced by the project (its "security requirements"). (URL required) ^{[documentation_security]}

These are the security requirements that the software is intended to meet.

The security policy.md clearly define how users can and can’t expect in terms of security from the software produced by the project. URL: https://github.com/KidiIT/Automation-repetitive-task-software/blob/main/SECURITY.md

Met

Unmet

N/A

?

The project MUST provide a "quick start" guide for new users to help them quickly do something with the software. (URL required) ^{[documentation_quick_start]}

The idea is to show users how to get started and make the software do anything at all. This is critically important for potential users to get started.

100% the software/ project provides a quick start guide for new users to help them quickly contribute or use my code. New users can go through the CONTRIBUTING.md file and Code of Conduct on the project Home Page. Also understanding how the project was build from the start will enable new users to understand In comprehensive and efficient in other to use the best of the software. Furthermore, New users can go through the security policy file to know the current status of the project in other to know which version the software supports and understand more how they can file a report on any vulnerability being exploited by users. URL: https://github.com/KidiIT/Automation-repetitive-task-software/blob/main/CONTRIBUTING.md URL: https://github.com/KidiIT/Automation-repetitive-task-software?tab=coc-ov-file#

Met

Unmet

N/A

?

The project MUST make an effort to keep the documentation consistent with the current version of the project results (including software produced by the project). Any known documentation defects making it inconsistent MUST be fixed. If the documentation is generally current, but erroneously includes some older information that is no longer true, just treat that as a defect, then track and fix as usual. ^{[documentation_current]}

The documentation MAY include information about differences or changes between versions of the software and/or link to older versions of the documentation. The intent of this criterion is that an effort is made to keep the documentation consistent, not that the documentation must be perfect.

the CodeQL tool which I installed on my project helps to keep the documentation with the current version of the project updated on a daily basis. It checks for faults and fixes any errors that might be found on the project. Also it regularly tracks and fix errors as usual. The url below explains how the CodeQL file was installed on the software to actively monitoring and updating of the software. URL: https://github.com/KidiIT/Automation-repetitive-task-software/blob/main/.github/CodeQL.yml

Met

Unmet

?

The project repository front page and/or website MUST identify and hyperlink to any achievements, including this best practices badge, within 48 hours of public recognition that the achievement has been attained. (URL required) ^{[documentation_achievements]}

An achievement is any set of external criteria that the project has specifically worked to meet, including some badges. This information does not need to be on the project website front page. A project using GitHub can put achievements on the repository front page by adding them to the README file.

In the best of my knowledge, I’ve attached the achievement made by the project on the project’s repository and website. Currently, my project has achieved The OpenSSF best practices badge (passing level) and a DOI badge. URL: https://github.com/KIDI-S-TECH/Automation-repetitive-task-software#automation-repetitive-task-software

Accessibility and internationalization

Met

Unmet

N/A

?

The project (both project sites and project results) SHOULD follow accessibility best practices so that persons with disabilities can still participate in the project and use the project results where it is reasonable to do so. ^{[accessibility_best_practices]}

For web applications, see the Web Content Accessibility Guidelines (WCAG 2.0) and its supporting document Understanding WCAG 2.0; see also W3C accessibility information. For GUI applications, consider using the environment-specific accessibility guidelines (such as Gnome, KDE, XFCE, Android, iOS, Mac, and Windows). Some TUI applications (e.g. `ncurses` programs) can do certain things to make themselves more accessible (such as `alpine`'s `force-arrow-cursor` setting). Most command-line applications are fairly accessible as-is. This criterion is often N/A, e.g., for program libraries. Here are some examples of actions to take or issues to consider:

Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language ( WCAG 2.0 guideline 1.1)
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. ( WCAG 2.0 guideline 1.4.1)
The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for large text, incidental text, and logotypes ( WCAG 2.0 guideline 1.4.3)
Make all functionality available from a keyboard (WCAG guideline 2.1)
A GUI or web-based project SHOULD test with at least one screen-reader on the target platform(s) (e.g. NVDA, Jaws, or WindowEyes on Windows; VoiceOver on Mac & iOS; Orca on Linux/BSD; TalkBack on Android). TUI programs MAY work to reduce overdraw to prevent redundant reading by screen-readers.

The aspect of this validation isn’t assessable in my project. Because my software isn’t a web application rather a software development tool which can be easily integrated into any application and it performs a monetary automation tasks in any business sector as specified on my project documentation. On the other hand, the project Accessibility and internationalization can be seen by my end-users in other to download and make use of the software @Zenodo website where I acquired a Digital object identification for my project which has a Creative Commons Attribution 4.0 International Right of Access for the Public to use in a digital device and a Right to Access for all users which is recognized internationally according to the International Copyright.

URL: https://zenodo.org/records/10829824

Met

Unmet

N/A

?

The software produced by the project SHOULD be internationalized to enable easy localization for the target audience's culture, region, or language. If internationalization (i18n) does not apply (e.g., the software doesn't generate text intended for end-users and doesn't sort human-readable text), select "not applicable" (N/A). ^{[internationalization]}

Localization "refers to the adaptation of a product, application or document content to meet the language, cultural and other requirements of a specific target market (a locale)." Internationalization is the "design and development of a product, application or document content that enables easy localization for target audiences that vary in culture, region, or language." (See W3C's "Localization vs. Internationalization".) Software meets this criterion simply by being internationalized. No localization for another specific language is required, since once software has been internationalized it's possible for others to work on localization.

The project possesses the Creative Commons Attribution 4.0 International Right. Which makes it internationally recognized that explains how recognition of the software by end-users. the work will be attributed to the real owner of the project according to the international standards right that govern the software.

URL: https://zenodo.org/records/10829824

Other

Met

Unmet

N/A

?

If the project sites (website, repository, and download URLs) store 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). If the project sites do not store passwords for this purpose, select "not applicable" (N/A). ^{[sites_password_security]}

Note that the use of GitHub meets this criterion. This criterion only applies to passwords used for authentication of external users into the project sites (aka inbound authentication). If the project sites must log in to other sites (aka outbound authentication), they may need to store authorization tokens for that purpose differently (since storing a hash would be useless). This applies criterion crypto_password_storage to the project sites, similar to sites_https.

To begin with, the project was built, designed and deployed on GitHub. The whole process was done using the GitHub interface. The ability of the website to have a form validation interface situated on the web site makes it possible for the project to store passwords for authentication of external users, the passwords can be stored or exported in a Bcrypt form. Making it more convenient and secure process. With HTTPS domain name protocol

Automation-repetitive-task-software

Basics 17/17 ●

Identification

Prerrequisitos

Basic project website content

Supervisión del proyecto

Documentation

Accessibility and internationalization

Other

Change Control 1/1 ●

Versiones anteriores

Informes 3/3 ●

Bug-reporting process

Proceso de informe de vulnerabilidad

Calidad 19/19 ●

Coding standards

Working build system

Installation system

Externally-maintained components

Automated test suite

New functionality testing

Banderas de advertencia

Seguridad 13/13 ●

Conocimiento de desarrollo seguro

Use buenas prácticas criptográficas

Secure release

Otros problemas de seguridad

Analysis 2/2 ●

Análisis estático de código

Dynamic code analysis