Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v12.0.0, compatible with Protocol 21 #949

Merged
merged 8 commits into from
Apr 30, 2024
Merged

Release v12.0.0, compatible with Protocol 21 #949

merged 8 commits into from
Apr 30, 2024

Conversation

Shaptic
Copy link
Contributor

@Shaptic Shaptic commented Apr 29, 2024

No description provided.

@Shaptic Shaptic requested review from chadoh, leighmcculloch, sreuland and a team April 29, 2024 23:14
Copy link

Size Change: +44.8 kB (0%)

Total Size: 11.5 MB

Filename Size Change
dist/stellar-sdk.js 6.37 MB +25.6 kB (0%)
dist/stellar-sdk.min.js 5.12 MB +19.1 kB (0%)

compressed-size-action

Copy link

socket-security bot commented Apr 29, 2024

Copy link

socket-security bot commented Apr 29, 2024

🚨 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 NoteSource
Network access npm/mz@2.7.0
Filesystem access npm/mz@2.7.0
Filesystem access npm/husky@9.0.11
Native code npm/sodium-native@4.1.1
Filesystem access npm/envinfo@7.13.0

View full report↗︎

Next steps

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 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'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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/mz@2.7.0
  • @SocketSecurity ignore npm/husky@9.0.11
  • @SocketSecurity ignore npm/sodium-native@4.1.1
  • @SocketSecurity ignore npm/envinfo@7.13.0

@Shaptic Shaptic merged commit dedacda into master Apr 30, 2024
9 of 10 checks passed
@Shaptic Shaptic deleted the v12.0.0 branch April 30, 2024 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants