Closed dependabot[bot] closed 2 months ago
socket-security[bot]
commented
3 months ago New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/chalk@5.3.0, npm/chokidar@3.5.3, npm/clsx@2.1.0, npm/commander@11.1.0, npm/eslint-config-prettier@9.1.0, npm/espree@9.6.1, npm/glob@10.3.10, npm/lodash-es@4.17.21, npm/postcss@8.4.35, npm/react-dom@18.2.0, npm/react@18.2.0, npm/rimraf@5.0.5, npm/tslib@2.6.2, npm/typescript@5.3.3, npm/zod@3.22.4
socket-security[bot]
commented
3 months ago 🚨 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 |
|---|---|---|---|
| Install scripts | npm/@swc/core@1.3.101 |
|
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/@swc/core@1.3.101
dependabot[bot]
commented
2 months ago Superseded by #57.
Bumps @storm-software/linting-tools from 1.38.13 to 1.44.1.
Release notes
Sourced from
@storm-software/linting-tools's releases.... (truncated)
Changelog
Sourced from
@storm-software/linting-tools's changelog.... (truncated)
Commits
bffe60fchore(release): Publish monorepo release updates42e5a41fix(storm-workspace): Resolved issue with failed unit-test30b8445chore(release): Publish monorepo release updates06ec9a6feat(workspace-tools): Major updates to base nx.json configurationdaf28aafix(git-tools): Resolved issues withleft-hookscripts5738161feat(workspace-tools): Added Nx plugin to apply rust and typescript targetsdf52eecchore(release): Publish monorepo release updatesc35e249fix(linting-tools): Update the linting-tools asset configuration5ad2038chore(release): Publish monorepo release updates24c984efeat(linting-tools): Added thetaploandls-linttoolsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show