1.Shebang

#!/SBUILD

#!/SBUILD ver @v0.4.5 #Asserts Builder/Linter's Version
_disabled: false #Tells the Interpreter to run it

• It starts with #!/SBUILD ver @${VERSION} (TYPE: RECOMMENDED)

• It is followed by _disabled: boolean, which can either be true or false which will disable or enable the entire script, respectively. (TYPE: ENFORCED)

• If it is disabled ( _disabled: true ), it is RECOMMENDED to specify a reason:

• abandoned (SBUILD No Has Any Active Maintainer)

_disabled: true #Denotes this SBUILD has been Disabled

#If abandoned by a Maintainer (& No other Maintainers are willing to take-over), specify a Date & Explanation/Reason/Reference
_disabled_reason:
   abandoned:
     - date: "2024-12-31" #YYYY-MM-DDTHH:MM:SSZ [RFC 3339], or if that's not possible then just YYYY-MM-DD
       reason: "Maintainer @${USERNAME} no longer wants to maintain it" #Just an example of a Valid reason

---

• broken (SBUILD No Longer Builds/Compiles)

_disabled: true #Denotes this SBUILD has been Disabled

#If broken, specify a Date & Explanation/Reason/Reference
_disabled_reason:
   broken:
     - date: "2024-12-31" #YYYY-MM-DDTHH:MM:SSZ [RFC 3339], or if that's not possible then just YYYY-MM-DD
       reason: "No Longer Builds, All attempts to fix were unsuccessful" #Just an example of a Valid reason

---

• deprecated (SBUILD 's Upstream Has been Abandoned/Archived/Deprecated)

_disabled: true #Denotes this SBUILD has been Disabled

#If deprecated (archived/abandoned), specify a Date & Explanation/Reason/Reference
_disabled_reason:
   deprecated:
     - date: "2024-12-31" #YYYY-MM-DDTHH:MM:SSZ [RFC 3339], or if that's not possible then just YYYY-MM-DD
       reason: "Upstream Repo was archived & Project Discontinued" #Just an example of a Valid reason

---

• dmca (SBUILD 's Upstream Has send a Copyright/Cease&Desist/DMCA Notice)

_disabled: true #Denotes this SBUILD has been Disabled

#If told to cease & desist due to copyright, dmca or license; specify a Date & Explanation/Reason/Reference
_disabled_reason:
   dmca:
     - date: "2024-12-31" #YYYY-MM-DDTHH:MM:SSZ [RFC 3339], or if that's not possible then just YYYY-MM-DD
       reason: "Upstream sent us a Cease & Desist Notice" #This should also contain a Link to the Discussion/Issue where Upstream sent the notice

---

• insecure (SBUILD 's Upstream Has a Serious Security Vulnerability)

_disabled: true #Denotes this SBUILD has been Disabled

#If Insecure (A CVE or something else), specify a Date & Explanation/Reason/Reference
_disabled_reason:
   insecure:
     - date: "2024-12-31" #YYYY-MM-DDTHH:MM:SSZ [RFC 3339], or if that's not possible then just YYYY-MM-DD
       reason: "Upstream Repo was caught spreading Malware" #Just an example of a Valid reason

---

• replaced (SBUILD has been Replaced by Another SBUILD )

_disabled: true #Denotes this SBUILD has been Disabled

#If Replaced (With another SBUILD/pkg), specify a Date, the new PKG_ID & Explanation/Reason/Reference
_disabled_reason:
   replaced:
     - date: "2024-12-31" #YYYY-MM-DDTHH:MM:SSZ [RFC 3339], or if that's not possible then just YYYY-MM-DD
       pkg_id: "foo.com.bar" #This MUST be a VALID PKG_ID of an already existing pkg
       reason: "Existing package is no longer maintained" #Just an example of a Valid reason

---

• Finally, if it is NOT any of the reason listed above, it is also okay to specify a simple one:

_disabled: true #Denotes this SBUILD has been Disabled
#If it doesn't fit any other category listed above
_disabled_reason:
  - "# A custom reason"
  #It is possible to have multiple reasons