Closed dependabot[bot] closed 4 months ago
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
Package | New capabilities | Transitives | Size | Publisher |
---|---|---|---|---|
npm/@angular-devkit/build-angular@16.2.12 | environment, filesystem, network, shell, unsafe Transitive: eval | +210 |
76.7 MB | google-wombot |
🚮 Removed packages: npm/@angular-devkit/build-angular@16.2.10
🚨 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 |
---|---|---|---|
Native code | npm/fsevents@1.2.13 |
| |
Install scripts | npm/fsevents@1.2.13 |
|
Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.
Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.
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/fsevents@1.2.13
OK, I won't notify you again about this release, but will get in touch when a new version is available.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
Bumps vite to 4.5.2 and updates ancestor dependency @angular-devkit/build-angular. These dependencies need to be updated together.
Updates
vite
from 4.4.7 to 4.5.2Changelog
Sourced from vite's changelog.
... (truncated)
Commits
d0360c1
release: v4.5.2eeec23b
fix: fs deny for case insensitive systems (#15653)c075115
release: v4.5.141bb354
fix: backport #15223, proxy html path should be encoded (#15226)055d2b8
release: v4.5.0ed7bdc5
feat: scan .marko files (#14669)45595ef
feat: backport mdx as known js source (#14560) (#14670)520139c
feat(ssr): backport ssr.resolve.conditions and ssr.resolve.externalConditions...b50db04
release: v4.4.1154e1275
revert: "fix: use string manipulation instead of regex to inject esbuild helpersUpdates
@angular-devkit/build-angular
from 16.2.10 to 16.2.12Release notes
Sourced from
@angular-devkit/build-angular
's releases.Changelog
Sourced from
@angular-devkit/build-angular
's changelog.... (truncated)
Commits
c306f73
release: cut the v16.2.12 release5fad401
fix(@angular-devkit/build-angular
): update dependency vite to v4.5.275ab5fa
release: cut the v16.2.11 release8314369
test: always use package manager force option in version add command E2Ee0e011f
build: update dependency vite to v4.5.1Dependabot 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