Closed DerekNonGeneric closed 3 months ago
Sweep is currently reviewing your pr...
New and removed dependencies detected. Learn more about Socket for GitHub โ๏ธ
๐ฎ Removed packages: npm/env-cmd@10.1.0, npm/eslint-config-biome@1.5.3, npm/eslint-plugin-json@3.1.0, npm/eslint-plugin-markdown@4.0.1, npm/eslint@9.0.0, npm/nps-i@1.0.2, npm/nps-utils@1.7.0, npm/postcss-html@1.6.0, npm/remark-lint-maximum-line-length@4.0.0, npm/stylelint-config-recess-order@5.0.0, npm/stylelint@16.3.1, npm/zx@8.0.1
๐จ 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.64 |
| |
Install scripts | npm/es5-ext@0.10.64 |
| |
Install scripts | npm/dprint@0.45.1 |
| |
Install scripts | npm/@biomejs/biome@1.7.1 |
|
|
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.
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 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.
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.
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.64
@SocketSecurity ignore npm/dprint@0.45.1
@SocketSecurity ignore npm/@biomejs/biome@1.7.1
as many of you know, we have plenty of work to go around and not really enough people available to do it and this is the kind of work that excites me personally, so let's dig in (we'll see how far we get tonight)
let's first address the notice above, which is bout socket detecting protestware, which should be long over-due for fixes
i think for a while we did not address this since it did not affect us, but i want this fixed already and i know that we can do so
i am going to do this by looking for the package in question in our package-lock.yaml
:
okay, this seems like it goes all the way back to a dependency of the published version of @openinf/util-text
if we can simply use the repo in its current state (or a branch like next
) rather than published version, we seem like we will be out of the woods here — i am going to work on something like that next if anyone wants to peep that, y'all can check:
i wanted to bring these changes back here and add something like the below image to the main page
like the footer from jekyllrb.com