fix: add version property as mandatory

Add version property as mandatory in validate_artifact function.

CHANGELOG.md

@@ -47,15 +47,19 @@ All notable changes to this project will be documented in this file.
 - `memory_dump/coredump.yaml`: Added collection of core dump, ABRT, Apport, and kdump files [esxi, linux, netbsd]. (by [mnrkbys](https://github.com/mnrkbys))
 
 ### Changed
+
 - `files/logs/macos_unified_logs.yaml`: Updated to include collection of ASL logs [macos]. (by [Pierre-Gronau-ndaal](https://github.com/Pierre-Gronau-ndaal))
 - `live_response/packages/dpkg.yaml`: Updated to validate all installed packages by comparing the installed files against the package metadata stored in the dpkg database [linux]. (by [Pierre-Gronau-ndaal](https://github.com/Pierre-Gronau-ndaal))
 - `live_response/packages/snap.yaml`: Updated collection to display installed packages including all revisions [linux]. (by [Pierre-Gronau-ndaal](https://github.com/Pierre-Gronau-ndaal))
 
 ### Fixed
+
 - Resolved an issue where the `hash` and `stat` collectors failed to function correctly when the `%user_home%` variable was included in the path property. ([#289](https://github.com/tclahr/uac/issues/289))
 
 ### Profiles
+
 - Added `offline_ir_triage.yaml`: New 'offline_ir_triage' profile for offline triage collections. (by [clausing](https://github.com/clausing))
 
 ### New Artifact Properties
+
 - Introduced `redirect_stderr_to_stdout`: When enabled, this property redirects error messages (stderr) to standard output (stdout). Useful for debugging and ensuring complete logs.

CODE_OF_CONDUCT.md

@@ -1,3 +1,5 @@
+# Code of Conduct
+
 An open-source and open community project is one in which participants choose to work together, and in that process experience differences in language, location, nationality, and experience. In such a diverse environment, misunderstandings and disagreements happen, which in most cases can be resolved informally. In rare cases, however, behavior can intimidate, harass, or otherwise disrupt one or more people in the community, which this project will not tolerate.
 
 A **Code of Conduct** is useful to define accepted and acceptable behaviors and to promote high standards of professional practice. It also provides a benchmark for self evaluation and acts as a vehicle for better identity of the organization.
@@ -7,7 +9,9 @@ This code (**CoC**) applies to any participant in this project's community – d
 ## Statement of Intent
 
 This project is committed to maintain a **positive** [work environment](#work-environment). This commitment calls for a workplace where [participants](#participant) at all levels behave according to the rules of the following code. A foundational concept of this code is that we all share responsibility for our work environment.
+
 ## Code
+
 1. Treat each other with [respect](#respect), professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.
 1. Never [harass](#harassment) or [bully](#workplace-bullying) anyone verbally, physically or [sexually](#sexual-harassment).
 1. Never [discriminate](#discrimination) on the basis of personal characteristics or group membership.
@@ -21,37 +25,50 @@ This project is committed to maintain a **positive** [work environment](#work-en
 1. Step down considerately: Members of every project come and go, and the Hyperledger Project is no different. When you leave or disengage from the project, in whole or in part, we ask that you do so in a way that minimizes disruption to the project. This means you should tell people you are leaving and take the proper steps to ensure that others can pick up where you left off.
 
 ## Glossary
-#### Demeaning behavior
+
+### Demeaning behavior
+
 is acting in a way that reduces another person's dignity, sense of self-worth or respect within the community.
 
-#### Discrimination
+### Discrimination
+
 is the prejudicial treatment of an individual based on criteria such as: physical appearance, race, ethnic origin, genetic differences, national or social origin, name, religion, gender, sexual orientation, family or health situation, pregnancy, disability, age, education, wealth, domicile, political view, morals, employment, or union activity.
 
-#### Insulting behavior
+### Insulting behavior
+
 is treating another person with scorn or disrespect.
 
-#### Acknowledgement
+### Acknowledgement
+
 is a record of the origin(s) and author(s) of a contribution.
 
-#### Harassment
+### Harassment
+
 is any conduct, verbal or physical, that has the intent or effect of interfering with an individual, or that creates an intimidating, hostile, or offensive environment.
 
-#### Leadership position
+### Leadership position
+
 includes group Chairs, project maintainers, staff members, and Board members.
 
-#### Participant
+### Participant
+
 includes the following persons:
+
 * Developers
 * Anyone from the Public partaking in this project's work environment (e.g. contribute code, comment on our code or specs, email us, attend our conferences, functions, etc)
 
-#### Respect
+### Respect
+
 is the genuine consideration you have for someone (if only because of their status as participant in Hyperledger Project, like yourself), and that you show by treating them in a polite and kind way.
 
-#### Sexual harassment
+### Sexual harassment
+
 includes visual displays of degrading sexual images, sexually suggestive conduct, offensive remarks of a sexual nature, requests for sexual favors, unwelcome physical contact, and sexual assault.
 
-#### Unwelcome behavior
+### Unwelcome behavior
+
 Hard to define? Some questions to ask yourself are:
+
 * how would I feel if I were in the position of the recipient?
 * would my spouse, parent, child, sibling or friend like to be treated this way?
 * would I like an account of my behavior published in the organization's newsletter?
@@ -61,21 +78,25 @@ Hard to define? Some questions to ask yourself are:
 
 _Summary_: if you are unsure whether something might be welcome or unwelcome, don't do it.
 
-#### Unwelcome sexual advance
+### Unwelcome sexual advance
+
 includes requests for sexual favors, and other verbal or physical conduct of a sexual nature, where:
+
 * submission to such conduct is made either explicitly or implicitly a term or condition of an individual's employment,
 * submission to or rejection of such conduct by an individual is used as a basis for employment decisions affecting the individual,
 * such conduct has the purpose or effect of unreasonably interfering with an individual's work performance or creating an intimidating hostile or offensive working environment.
 
-#### Workplace Bullying
+### Workplace Bullying
+
 is a tendency of individuals or groups to use persistent aggressive or unreasonable behavior (e.g. verbal or written abuse, offensive conduct or any interference which undermines or impedes work) against a co-worker or any professional relations.
 
-#### Work Environment
+### Work Environment
+
 is the set of all available means of collaboration, including, but not limited to messages to mailing lists, private correspondence, Web pages, chat channels, phone and video teleconferences, and any kind of face-to-face meetings or discussions.
 
 ## Incident Procedure
 
-To report incidents or to appeal reports of incidents, send email to iplsdk@linux.vnet.ibm.com create email. Please include any available relevant information, including links to any publicly accessible material relating to the matter. Every effort will be taken to ensure a safe and collegial environment in which to collaborate on matters relating to the Project. In order to protect the community, the Project reserves the right to take appropriate action, potentially including the removal of an individual from any and all participation in the project. The Project will work towards an equitable resolution in the event of a misunderstanding.
+To report incidents or to appeal reports of incidents, send email to <iplsdk@linux.vnet.ibm.com> create email. Please include any available relevant information, including links to any publicly accessible material relating to the matter. Every effort will be taken to ensure a safe and collegial environment in which to collaborate on matters relating to the Project. In order to protect the community, the Project reserves the right to take appropriate action, potentially including the removal of an individual from any and all participation in the project. The Project will work towards an equitable resolution in the event of a misunderstanding.
 
 ## Credits
 

CONTRIBUTING.md

@@ -146,9 +146,9 @@ To ensure consistency throughout the source code, keep these rules in mind as yo
 
 We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history.
 
-Each commit message consists of a **header**, a **blank line** and a **body**. The header has a special format that includes a **type** and a **subject**. 
+Each commit message consists of a **header**, a **blank line** and a **body**. The header has a special format that includes a **type** and a **subject**.
 
-```
+```text
 <type>: <subject>
 <BLANK LINE>
 <body>
@@ -158,7 +158,7 @@ Any line of the commit message cannot be longer than 100 characters! This allows
 
 Samples:
 
-```
+```text
 docs: update changelog to v2.0.0
 fix: fixed issue #15
 ```

LICENSES.md

@@ -1,8 +1,10 @@
+# Licenses
+
 Use of the following Third-Party Software is subject to the license agreements at the URLs listed in the table below.
 
 |Product|Copyright|URL|
 |---|---|---|
-|AVML|Use rights in accordance with the information displayed at: https://github.com/microsoft/avml/blob/main/LICENSE|https://github.com/microsoft/avml|
-|linux_procmemdump.sh|Use rights in accordance with the information displayed at: https://creativecommons.org/licenses/by-sa/4.0|
-|statx|Use rights in accordance with the information displayed at: https://github.com/tclahr/statx/blob/main/LICENSE|https://github.com/tclahr/statx|
-|zip|Use rights in accordance with the information displayed at: https://infozip.sourceforge.net/license.html|https://infozip.sourceforge.net|
+|AVML|Use rights in accordance with the information displayed at: <https://github.com/microsoft/avml/blob/main/LICENSE>|<https://github.com/microsoft/avml>|
+|linux_procmemdump.sh|Use rights in accordance with the information displayed at: <https://creativecommons.org/licenses/by-sa/4.0>||
+|statx|Use rights in accordance with the information displayed at: <https://github.com/tclahr/statx/blob/main/LICENSE>|<https://github.com/tclahr/statx>|
+|zip|Use rights in accordance with the information displayed at: <https://infozip.sourceforge.net/license.html>|<https://infozip.sourceforge.net>|

README.md

@@ -1,3 +1,5 @@
+<!-- markdownlint-disable MD033 -->
+<!-- markdownlint-disable MD041 -->
 <p align="center">
   <picture>
     <source media="(prefers-color-scheme: dark)" srcset="logo/uac-light.svg">
@@ -8,13 +10,13 @@
 
   <p align="center">
     <a href="https://github.com/tclahr/uac/actions/workflows/shellcheck.yaml" alt="Issues">
-      <img src="https://github.com/tclahr/uac/actions/workflows/shellcheck.yaml/badge.svg" /></a>
+      <img src="https://github.com/tclahr/uac/actions/workflows/shellcheck.yaml/badge.svg" alt="shellcheck_badge"/></a>
     <a href="https://bestpractices.coreinfrastructure.org/projects/5640" alt="CII Best Practices">
-      <img src="https://bestpractices.coreinfrastructure.org/projects/5640/badge" /></a>
+      <img src="https://bestpractices.coreinfrastructure.org/projects/5640/badge" alt="bestpractices_badge"/></a>
     <a href="https://github.com/tclahr/uac/releases" alt="GitHub release (latest by date including pre-releases)">
-      <img src="https://img.shields.io/github/v/release/tclahr/uac?include_prereleases&style=flat-square" /></a>
+      <img src="https://img.shields.io/github/v/release/tclahr/uac?include_prereleases&style=flat-square" alt="release_badge"/></a>
     <a href="https://github.com/tclahr/uac/LICENSE" alt="License">
-      <img src="https://img.shields.io/github/license/tclahr/uac?style=flat-square" /></a>
+      <img src="https://img.shields.io/github/license/tclahr/uac?style=flat-square" alt="license_badge"/></a>
   </p>
 
   <p align="center">
@@ -34,16 +36,18 @@
     •
     <a href="#-license">License</a>
   </p>
-
 </p>
+<!-- markdownlint-enable MD033 -->
+<!-- markdownlint-enable MD041 -->
 
 ## 🔎 About UAC
 
 **UAC (Unix-like Artifacts Collector)** is a powerful and extensible incident response tool designed for forensic investigators, security analysts, and IT professionals. It automates the collection of artifacts from a wide range of Unix-like systems, including AIX, ESXi, FreeBSD, Linux, macOS, NetBSD, NetScaler, OpenBSD and Solaris.
 
 Whether you're handling an intrusion, conducting forensic investigations, or performing compliance checks, UAC simplifies and accelerates data collection while minimizing reliance on external support during critical incidents.
 
-### Key Highlights:
+### Key Highlights
+
 - 📂 Fully customizable via YAML profiles for tailored data collection.
 - ⚡ Lightweight, portable, and requires no installation or dependencies.
 - 🔒 Adheres to the order of volatility to ensure reliable data acquisition.
@@ -87,27 +91,32 @@ UAC runs on any Unix-like system, regardless of the processor architecture. All
 UAC does not need to be installed on the target system. Simply download the latest version from the [releases page](https://github.com/tclahr/uac/releases), uncompress it, and launch. It's that simple!
 
 ### 🛠 Getting Started
+
 1. Download the latest release from the [Releases page](https://github.com/tclahr/uac/releases).
 2. Uncompress the archive.
 3. Execute the tool directly from the terminal.
 
 ### Examples
 
+<!-- markdownlint-disable MD033 -->
 <details>
 <summary>Click to view usage examples</summary>
 
 **Collect all artifacts based on the ir_triage profile:**
-```bash
+
+```shell
 ./uac -p ir_triage /tmp
 ```
 
 **Collect memory dump and all artifacts based on the full profile:**
-```bash
+
+```shell
 ./uac -a ./artifacts/memory_dump/avml.yaml -p full /tmp
 ```
 
 **Collect all artifacts excluding a specific one:**
-```bash
+
+```shell
 ./uac -p full -a \!artifacts/bodyfile/bodyfile.yaml .
 ```
 
@@ -124,6 +133,7 @@ UAC does not need to be installed on the target system. Simply download the late
 ```
 
 </details>
+<!-- markdownlint-enable MD033 -->
 
 ## 💙 Contributing
 

lib/find_based_collector.sh

@@ -283,5 +283,5 @@ _find_based_collector()
       fi
       ;;
   esac
- 
+
 }

lib/list_artifacts.sh

@@ -18,12 +18,14 @@ _list_artifacts()
     return 1
   fi
 
-  if [ "${__la_os}" = "all" ] || _is_in_list "${__la_os}" "aix|esxi|freebsd|linux|macos|netbsd|netscaler|openbsd|solaris"; then
-    true
-  else
-    _error_msg "list artifacts: invalid operating system '${__la_os}'"
-    return 1
-  fi
+  case "${__la_os}" in
+    all|aix|esxi|freebsd|linux|macos|netbsd|netscaler|openbsd|solaris)
+      ;;
+    *)
+      _error_msg "list artifacts: invalid operating system '${__la_os}'"
+      return 1
+      ;;
+  esac
 
   # Get artifacts for all or a specific operating system.
   # Arguments:
@@ -36,29 +38,22 @@ _list_artifacts()
     __oa_artifacts_dir="${1:-}"
     __oa_os="${2:-all}"
 
-    if [ "${__oa_os}" = "all" ]; then
-      # shellcheck disable=SC2162
-      find "${__oa_artifacts_dir}"/* -name "*.yaml" -print 2>/dev/null \
-        | while read __oa_item || [ -n "${__oa_item}" ]; do
-            if grep -q -E "modifier:.*true" "${__oa_item}" 2>/dev/null; then
-              echo "${__oa_item} (modifier)" | sed -e "s|^${__oa_artifacts_dir}/||" 2>/dev/null
-            else
-              echo "${__oa_item}" | sed -e "s|^${__oa_artifacts_dir}/||" 2>/dev/null
-            fi
-          done
-    else
-      # shellcheck disable=SC2162
-      find "${__oa_artifacts_dir}"/* -name "*.yaml" -print 2>/dev/null \
-        | while read __oa_item || [ -n "${__oa_item}" ]; do
-            if grep -q -E "supported_os:.*all|${__oa_os}" "${__oa_item}" 2>/dev/null; then
-              if grep -q -E "modifier:.*true" "${__oa_item}" 2>/dev/null; then
-                echo "${__oa_item} (modifier)" | sed -e "s|^${__oa_artifacts_dir}/||" 2>/dev/null
-              else
-                echo "${__oa_item}" | sed -e "s|^${__oa_artifacts_dir}/||" 2>/dev/null
-              fi
-            fi
-          done
-    fi
+    # shellcheck disable=SC2162
+    find "${__oa_artifacts_dir}"/* -name "*.yaml" -print 2>/dev/null \
+      | sort -u \
+      | while read __oa_item || [ -n "${__oa_item}" ]; do
+          __oa_modifier=""
+
+          if grep -q -E "modifier:.*true" "${__oa_item}" 2>/dev/null; then
+            __oa_modifier=" (modifier)"
+          fi
+
+          if [ "${__oa_os}" = "all" ] || grep -q -E "supported_os:.*(all|${__oa_os})" "${__oa_item}"; then
+            __oa_filename=`echo "${__oa_item}" | sed -e "s|^${__oa_artifacts_dir}/||" 2>/dev/null`
+            echo "${__oa_filename}${__oa_modifier}"
+          fi
+        done
+
   }
 
   __la_selected_artifacts=`_get_operating_system_artifact_list "${__la_artifacts_dir}" "${__la_os}"`

lib/remove_non_regular_files.sh

@@ -14,7 +14,7 @@ _remove_non_regular_files()
     _log_msg ERR "_remove_non_regular_files: no such file or directory '${__rn_file}'"
     return 1
   fi
- 
+
   if [ ! -s "${__rn_file}" ]; then
     _log_msg DBG "_remove_non_regular_files: skipping empty file '${__rn_file}'"
     return 1

lib/run_command.sh

@@ -41,5 +41,5 @@ _run_command()
   fi
 
   return "${__rc_exit_code}"
- 
+
 }

lib/usage.sh

@@ -8,10 +8,10 @@
 #   none
 _usage()
 {
-  printf "%s" "Usage: $0 [-h] [-V] [--debug] {-p PROFILE | -a ARTIFACT} DESTINATION 
-             
-   or: $0 --validate-artifact FILE
-   or: $0 --validate-profile FILE
+  printf "%s" "Usage: $0 [-h] [-V] [--debug] {-p PROFILE | -a ARTIFACT} DESTINATION
+
+  or: $0 --validate-artifact FILE
+  or: $0 --validate-profile FILE
 
 Optional Arguments:
   -h, --help        Display this help and exit.
@@ -59,7 +59,7 @@ Collection Arguments:
   -s, --operating-system OPERATING_SYSTEM
                     Specify the operating system.
                     Options: aix, esxi, freebsd, linux, macos, netbsd
-                             netscaler, openbsd, solaris
+                      netscaler, openbsd, solaris
   -H, --hash-collected
                     Hash all collected files.
   -u, --run-as-non-root
@@ -69,7 +69,7 @@ Collection Arguments:
                     Enable artifacts that change the system state.
       --hostname  HOSTNAME
                     Specify the target system hostname.
-      --temp-dir  PATH   
+      --temp-dir  PATH
                     Write all temporary data to this directory.
 
 Filter Arguments: