Bump the npm_and_yarn group with 9 updates
Bumps the npm_and_yarn group with 9 updates:
| Package | From | To |
|---|---|---|
| braces | 3.0.2 |
3.0.3 |
| browserify-sign | 4.2.1 |
4.2.3 |
| cross-spawn | 7.0.3 |
7.0.6 |
| elliptic | 6.5.4 |
6.6.1 |
| json5 | 1.0.1 |
1.0.2 |
| micromatch | 4.0.5 |
4.0.8 |
| semver | 6.3.0 |
6.3.1 |
| tar | 6.1.12 |
6.2.1 |
| word-wrap | 1.2.3 |
1.2.5 |
Updates braces from 3.0.2 to 3.0.3
Commits
74b2db23.0.388f1429update eslint. lint, fix unit tests.415d660Snyk js braces 6838727 (#40)190510ffix tests, skip 1 test in test/braces.expand716eb9freadme bumpa5851e5Merge pull request #37 from coderaiser/fix/vulnerability2092bd1feature: braces: add maxSymbols (https://github.com/micromatch/braces/issues/...9f5b4cffix: vulnerability (https://security.snyk.io/vuln/SNYK-JS-BRACES-6838727)98414f9remove funding file665ab5dupdate keepEscaping doc (#27)- Additional commits viewable in compare view
Updates browserify-sign from 4.2.1 to 4.2.3
Changelog
Sourced from browserify-sign's changelog.
v4.2.3 - 2024-03-05
Commits
- [patch] widen support to 0.12
9247adf- [patch] drop minimum node support to v1
4d0ee49- [Dev Deps] update
aud,npmignore,tape87f3a35- [actions] remove redundant finisher
37a4758- [Deps] pin
hash-baseto ~3.0, due to a breaking change9e2bf12- [Deps] update
parse-asn1 [f427270`](https://github.com/browserify/browserify-sign/commit/f427270ac11dc6be29f87d7afb046c16376a5a9c)- [Deps] update
ellipticfb261ce- [Deps] pin
ellipticdue to a breaking change168e16fv4.2.2 - 2023-10-25
Fixed
- [Tests] log when openssl doesn't support cipher
[#37](https://github.com/crypto-browserify/browserify-sign/issues/37)Commits
- Only apps should have lockfiles
09a8995- [eslint] switch to eslint
83fe463- [meta] add
npmignoreandauto-changelog4418183- [meta] fix package.json indentation
9ac5a5e- [Tests] migrate from travis to github actions
d845d85- [Fix]
sign: throw on unsupported padding scheme8767739- [Fix] properly check the upper bound for DSA signatures
85994cd- [Tests] handle openSSL not supporting a scheme
f5f17c2- [Deps] update
bn.js,browserify-rsa,elliptic,parse-asn1,readable-stream,safe-buffera67d0eb- [Dev Deps] update
nyc,standard,tapecc5350b- [Tests] always run coverage; downgrade
nyc75ce1d5- [meta] add
safe-publish-latestdcf49ce- [Tests] add
npm run posttest75dd8fd- [Dev Deps] update
tape3aec038- [Tests] skip unsupported schemes
703c83e- [Tests] node < 6 lacks array
includes3aa43cf- [Dev Deps] fix eslint range
98d4e0d
Commits
bf2c3ecv4.2.39247adf[patch] widen support to 0.12f427270[Deps] update `parse-asn187f3a35[Dev Deps] updateaud,npmignore,tapefb261ce[Deps] updateelliptic4d0ee49[patch] drop minimum node support to v19e2bf12[Deps] pinhash-baseto ~3.0, due to a breaking change168e16f[Deps] pinellipticdue to a breaking change37a4758[actions] remove redundant finisher4af5a90v4.2.2- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by ljharb, a new releaser for browserify-sign since your current version.
Updates cross-spawn from 7.0.3 to 7.0.6
Changelog
Sourced from cross-spawn's changelog.
7.0.6 (2024-11-18)
Bug Fixes
- update cross-spawn version to 7.0.5 in package-lock.json (f700743)
7.0.5 (2024-11-07)
Bug Fixes
- fix escaping bug introduced by backtracking (640d391)
7.0.4 (2024-11-07)
Bug Fixes
Commits
77cd97fchore(release): 7.0.66717de4chore: upgrade standard-versionf700743fix: update cross-spawn version to 7.0.5 in package-lock.json9a7e3b2chore: fix build status badge0852683chore(release): 7.0.5640d391fix: fix escaping bug introduced by backtrackingbff0c87chore: remove codecova7c6abcchore: replace travis with github workflows9b9246echore(release): 7.0.45ff3a07fix: disable regexp backtracking (#160)- Additional commits viewable in compare view
Updates elliptic from 6.5.4 to 6.6.1
Commits
Updates json5 from 1.0.1 to 1.0.2
Changelog
Sourced from json5's changelog.
Unreleased [code, diff]
v2.2.3 [code, diff]
- Fix: [email protected] is now the 'latest' release according to npm instead of v1.0.2. (#299)
v2.2.2 [code, diff]
- Fix: Properties with the name
__proto__are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).v2.2.1 [code, diff]
- Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)
v2.2.0 [code, diff]
- New: Accurate and documented TypeScript declarations are now included. There is no need to install
@types/json5. (#236, #244)v2.1.3 [code, diff]
v2.1.2 [code, diff]
... (truncated)
Commits
a62db1e1.0.2e0c23fedocs: update CHANGELOG for v1.0.262a6540fix: add proto to objects and arrays- See full diff in compare view
Updates micromatch from 4.0.5 to 4.0.8
Release notes
Sourced from micromatch's releases.
4.0.8
Ultimate release that fixes both CVE-2024-4067 and CVE-2024-4068. We consider the issues low-priority, so even if you see automated scanners saying otherwise, don't be scared.
Changelog
Sourced from micromatch's changelog.
[4.0.8] - 2024-08-22
- backported CVE-2024-4067 fix (from v4.0.6) over to 4.x branch
[4.0.7] - 2024-05-22
- this is basically v4.0.5, with some README updates
- it is vulnerable to CVE-2024-4067
- Updated braces to v3.0.3 to avoid CVE-2024-4068
- does NOT break API compatibility
[4.0.6] - 2024-05-21
- Added
hasBracesto check if a pattern contains braces.- Fixes CVE-2024-4067
- BREAKS API COMPATIBILITY
- Should be labeled as a major release, but it's not.
Commits
8bd704e4.0.8a0e6841run verb to generate README documentation4ec2884Merge branch 'v4' into hauserkristof-feature/v4.0.803aa805Merge pull request #266 from hauserkristof/feature/v4.0.8814f5f7lint67fcce6fix: CHANGELOG about braces & CVE-2024-4068, v4.0.5113f2e3fix: CVE numbers in CHANGELOGd9dbd9afeat: updated CHANGELOG2ab1315fix: use actions/setup-node@v41406ea3feat: rework test to work on macos with node 10,12 and 14- Additional commits viewable in compare view
Updates semver from 6.3.0 to 6.3.1
Release notes
Sourced from semver's releases.
v6.3.1
6.3.1 (2023-07-10)
Bug Fixes
928e56d#591 better handling of whitespace (#591) (@lukekarrys,@joaomoreno,@nicolo-ribaudo)
Changelog
Sourced from semver's changelog.
6.3.1 (2023-07-10)
Bug Fixes
928e56d#591 better handling of whitespace (#591) (@lukekarrys,@joaomoreno,@nicolo-ribaudo)6.2.0
- Coerce numbers to strings when passed to semver.coerce()
- Add
rtloption to coerce from right to left6.1.3
- Handle X-ranges properly in includePrerelease mode
6.1.2
- Do not throw when testing invalid version strings
6.1.1
- Add options support for semver.coerce()
- Handle undefined version passed to Range.test
6.1.0
- Add semver.compareBuild function
- Support
*in semver.intersects6.0
Fix
intersectslogic.This is technically a bug fix, but since it is also a change to behavior that may require users updating their code, it is marked as a major version increment.
5.7
- Add
minVersionmethod5.6
- Move boolean
looseparam to an options object, with backwards-compatibility protection.- Add ability to opt out of special prerelease version handling with the
includePrereleaseoption flag.5.5
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by lukekarrys, a new releaser for semver since your current version.
Updates tar from 6.1.12 to 6.2.1
Changelog
Sourced from tar's changelog.
Changelog
7.4
- Deprecate
onentryin favor ofonReadEntryfor clarity.7.3
- Add
onWriteEntryoption7.2
- DRY the command definitions into a single
makeCommandmethod, and update the type signatures to more appropriately infer the return type from the options and arguments provided.7.1
- Update minipass to v7.1.0
- Update the type definitions of
write()andend()methods onUnpackandParserclasses to be compatible with the NodeJS.WritableStream type in the latest versions of@types/node.7.0
- Rewrite in TypeScript, provide ESM and CommonJS hybrid interface
- Add tree-shake friendly exports, like
import('tar/create')andimport('tar/read-entry')to get individual functions or classes.- Add
chmodoption that defaults to false, and deprecatenoChmod. That is, reverse the default option regarding explicitly setting file system modes to match tar entry settings.- Add
processUmaskoption to avoid having to callprocess.umask()whenchmod: true(ornoChmod: false) is set.6.2
- Add support for brotli compression
- Add
maxDepthoption to prevent extraction into excessively deep folders.6.1
... (truncated)
Commits
bef7b1e6.2.1fe8cd57prevent extraction in excessively deep subfoldersfe7ebfdremove security.md5bc9d406.2.0fe1ef5echangelog 6.2e483220get rid of npm lint stuff689928aci that works outside of npm orgdb6f539file inference improvements for .tbr and .tgz336fa8frefactor: dry and other pr commentseeba222chore: lint fixes- Additional commits viewable in compare view
Updates word-wrap from 1.2.3 to 1.2.5
Release notes
Sourced from word-wrap's releases.
1.2.5
Changes:
Reverts default value for
options.indentto two spaces' '.Full Changelog: https://github.com/jonschlinkert/word-wrap/compare/1.2.4...1.2.5
1.2.4
What's Changed
- Remove default indent by
@mohd-akramin jonschlinkert/word-wrap#24- 🔒fix: CVE 2023 26115 (2) by
@OlafConijnin jonschlinkert/word-wrap#41- :lock: fix: CVE-2023-26115 by
@aashutoshrathiin jonschlinkert/word-wrap#33- chore: publish workflow by
@OlafConijnin jonschlinkert/word-wrap#42New Contributors
@mohd-akrammade their first contribution in jonschlinkert/word-wrap#24@OlafConijnmade their first contribution in jonschlinkert/word-wrap#41@aashutoshrathimade their first contribution in jonschlinkert/word-wrap#33Full Changelog: https://github.com/jonschlinkert/word-wrap/compare/1.2.3...1.2.4
Commits
207044e1.2.59894315revert default indentf64b188run verb to generate README03ea082Merge pull request #42 from jonschlinkert/chore/publish-workflow420dce9Merge pull request #41 from jonschlinkert/fix/CVE-2023-26115-2bfa694eUpdate .github/workflows/publish.ymlace0b3cchore: bump version to 1.2.46fd7275chore: add publish workflow30d6dafchore: fix test655929cchore: remove package-lock- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) -
@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) -
@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) -
@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency -
@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the Security Alerts page.
Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Package | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|
| npm/[email protected] | unsafe | 0 |
46.6 kB | indutny |
| npm/[email protected] | None | 0 |
44.6 kB | jonschlinkert |
| npm/[email protected] | None | 0 |
10.7 kB | ljharb |
| npm/[email protected] | Transitive: environment | +2 |
109 kB | ljharb |
| npm/[email protected] | environment, filesystem, shell | +1 |
26.1 kB | satazor |
| npm/[email protected] | None | 0 |
120 kB | indutny |
| npm/[email protected] | None | 0 |
16.7 kB | jonschlinkert |
| npm/[email protected] | None | 0 |
7.66 kB | ljharb |
| npm/[email protected] | None | 0 |
78.3 kB | jordanbtucker |
| npm/[email protected] | None | 0 |
56.6 kB | doowb |
| npm/[email protected] | None | 0 |
24.7 kB | ljharb |
| npm/[email protected] | environment, filesystem | +1 |
236 kB | isaacs |
| npm/[email protected] | None | 0 |
11.8 kB | jonschlinkert |
🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]
🚨 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 | CI |
|---|---|---|---|---|
| New author | npm/[email protected] | 🚫 | ||
| New author | npm/[email protected] | 🚫 | ||
| New author | npm/[email protected] | 🚫 |
Next steps
What is new author?
A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.
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/[email protected] or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/[email protected]@SocketSecurity ignore npm/[email protected]@SocketSecurity ignore npm/[email protected]