🐳✨：a Debian-Fisher-Gallium container collab (take 2)

[DerekNonGeneric]

Pull Request Purpose

Make a selection on the purpose(s) of your changes.

This PR contains the following:

• [x] 🐞🔧 bugfixing (🐜/🦟/🐛/🦗/🐝 et al.)
• [x] 🆕🎏 implementation of new feature(s)
• [x] ♻️ refactoring(s)
• [x] 📄 documentation modification(s)
• [x] 🔮 other

Testing

Have you included any tests in your submission?

• [x] yes (bugfixes and features will not be merged without tests)
• [ ] no

Breaking Changes

Have you modified any aspect public API surface (i.e., caused breakage)?

• [ ] yes (breaking changes will not be merged unless necessary)
• [x] no

Description

A concise recap summarily detailing what all are the changes being made.

we are in the communication blackout period, but once it's possible, please confirm we are all ready for takeoff on our Debian-based Docker container powered by Fisher plugins

/cc @jorgebucaran @OpenINF/ateamgrimesai

List of any relevant issue numbers:

• https://github.com/OpenINF/docker-fisher/issues/13

[DerekNonGeneric]

i will be landing https://github.com/OpenINF/docker-fisher/pull/32 very, very soon since this task seems dependent on its readiness

[OpenINFbot]

@DerekNonGeneric, well done!

here is a summary of what remains from the previous endeavor:

• properly setting a repo for Node.js
• migrating the remaining tasks to build/tasks/[...]
• turning those bash scripts into fish
• more-effectively linting/formatting
• shellcheck, aliases for simple (liteweight trash), etc.
• a little of tidying (we need a refactoring of some kind)

[DerekNonGeneric]

FYI: 🔗 https://containers.dev/implementors/json_reference/#min-host-reqs

:link: https://code.visualstudio.com/docs/setup/linux#_rhel-fedora-and-centos-based-distributions

i am going to be installing VS Code now too (recommend the same)

am looking into how, but i have no objection to vscodium:

• https://vscodium.com/

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@openinf/util-text@1.1.2	Transitive: environment, eval, shell	+18	859 kB	dereknongeneric
npm/zx@7.2.3	environment, filesystem Transitive: network, shell	+56	15 MB	google-wombot

🚮 Removed packages: npm/@yarnpkg/shell@4.0.0, npm/cspell@8.3.2, npm/editorconfig-checker@5.1.4, npm/remark-cli@12.0.0, npm/remark-validate-links@13.0.0, npm/stylelint-config-recess-order@4.6.0, npm/stylelint-config-standard-scss@13.0.0, npm/stylelint@16.2.1

View full report↗︎

[socket-security[bot]]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Protestware/Troll package	npm/es5-ext@0.10.62	Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale	package.json pnpm-lock.yaml
Install scripts	npm/es5-ext@0.10.62	Install script: postinstall Source: node -e "try{require('./_postinstall')}catch(e){}" || exit 0	package.json pnpm-lock.yaml

View full report↗︎

Next steps

What is protestware?

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Consider that consuming this package my come along with functionality unrelated to its primary purpose.

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/es5-ext@0.10.62

[DerekNonGeneric]

i am going to have to pull out some of this into a separate pr…

[DerekNonGeneric]

want to merge this asap for obvious reasons…

also is getting too large to review already

[DerekNonGeneric]

ok, really sorry, but we'll be needing a re-take