Fix #1321: private key in the protobuf functions

[samchon]

No description provided.

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/typia@1323

commit: 1a1778d

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@fastify/[email protected]	None	0	25.5 kB	matteo.collina
npm/@sinclair/[email protected]	None	0	536 kB	sinclair
npm/@trivago/[email protected]	Transitive: environment, filesystem, shell, unsafe	+35	12.6 MB	ayusharma
npm/@typegoose/[email protected]	environment Transitive: eval, filesystem, network	+101	15.5 MB	hasezoey
npm/@types/[email protected]	None	0	21.8 kB	types
npm/@types/[email protected]	None	0	9.24 kB	types
npm/@types/[email protected]	None	+31	1 MB	types
npm/@types/[email protected]	None	0	3.23 kB	types
npm/@types/[email protected]	None	0	6.67 kB	types
npm/@typescript-eslint/[email protected]	Transitive: environment, eval, filesystem, unsafe	+97	15.3 MB	jameshenry
npm/@typescript-eslint/[email protected]	Transitive: environment, eval, filesystem, unsafe	+90	12.1 MB	jameshenry
npm/[email protected]	environment, filesystem, network, shell Transitive: eval, unsafe	+34	2.92 MB	matteo.collina
npm/[email protected]	eval	+1	138 kB	jdalton
npm/[email protected]	None	0	776 kB	typestack-release-bot
npm/[email protected]	None	+3	14.3 MB	typestack-release-bot
npm/[email protected]	Transitive: filesystem, network, shell	+35	4.01 MB	mbostock
npm/[email protected]	Transitive: environment, eval, filesystem, unsafe	+96	13.8 MB	gund
npm/[email protected]	eval	+5	622 kB	jsumners
npm/[email protected]	Transitive: environment, eval, filesystem, unsafe	+49	5.7 MB	eomm
npm/[email protected]	None	+1	5.2 MB	gcanti
npm/[email protected]	eval, filesystem, network, shell, unsafe Transitive: environment	+46	7.46 MB	domenic
npm/[email protected]	shell	0	3.14 kB	seb
npm/[email protected]	environment, filesystem, unsafe	0	11.2 MB	prettier-bot
npm/[email protected]	None	0	295 kB	rbuckton
npm/[email protected]	Transitive: network	+4	695 kB	samchon
npm/[email protected]	None	0	667 kB	colinmcd94

🚮 Removed packages: npm/@emotion/[email protected], npm/@emotion/[email protected], npm/@monaco-editor/[email protected], npm/@mui/[email protected], npm/@mui/[email protected], npm/@rollup/[email protected], npm/@rspack/[email protected], npm/@rspack/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 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
Critical CVE	npm/@babel/[email protected]	CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: 7.23.2	benchmark/package.json	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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/@babel/[email protected]

[samchon]

No problem.