Release v11.4.0

[Shaptic]

Still needs merged PRs:

• Add transaction hash field to each item in the getEvents response #939
• yarn upgrade @stellar/stellar-base to match the P21 release

[github-actions]

Size Change: +2.26 kB (0%)

Total Size: 11.4 MB

Filename	Size	Change
dist/stellar-sdk.js	6.34 MB	+1.14 kB (0%)
dist/stellar-sdk.min.js	5.1 MB	+1.12 kB (0%)

_{compressed-size-action}

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@babel/[email protected]	None	0	65.2 kB	nicolo-ribaudo
npm/@babel/[email protected]	environment, filesystem, unsafe	+15	2.79 MB	nicolo-ribaudo
npm/@babel/[email protected]	None	+3	624 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	+7	555 kB	nicolo-ribaudo
npm/@babel/[email protected]	unsafe	+1	235 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	1.88 MB	nicolo-ribaudo
npm/@babel/[email protected]	environment, filesystem	+94	2.42 MB	nicolo-ribaudo
npm/@definitelytyped/[email protected]	environment, filesystem Transitive: network, shell	+137	49.5 MB	definitelytyped-publisher
npm/@types/[email protected]	None	0	192 kB	types
npm/@types/[email protected]	None	+1	2.1 MB	types
npm/[email protected]	None	0	727 kB	zloirock
npm/[email protected]	None	+43	3.26 MB	ljharb
npm/[email protected]	environment, filesystem, shell	0	3.61 kB	typicode
npm/[email protected]	environment, eval, filesystem	+40	3.88 MB	voxpelli
npm/[email protected]	None	0	247 kB	ljharb
npm/[email protected]	None	0	32.4 MB	typescript-bot

🚮 Removed packages: npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@definitelytyped/[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], 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
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	package.json
Network access	npm/[email protected]	Module: dns Location: Package overview	package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	package.json
Native code	npm/[email protected]	Location: Package overview	package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	package.json

View full report↗︎

Next steps

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What's wrong with native code?

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.

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]
• @SocketSecurity ignore npm/[email protected]