feat: update pump amm decoder with boost mode

[jshabo-dev]

No description provided.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​rustls@​0.23.40 ⏵ 0.23.41
	cargo/​quote@​1.0.45 ⏵ 1.0.46
	cargo/​borsh@​1.6.1 ⏵ 1.7.0
	cargo/​chrono@​0.4.44 ⏵ 0.4.45
	cargo/​env_logger@​0.11.10 ⏵ 0.11.11
	cargo/​log@​0.4.30 ⏵ 0.4.33
	cargo/​prost@​0.14.3 ⏵ 0.14.4
	cargo/​prost-types@​0.14.3 ⏵ 0.14.4
	cargo/​solana-hash@​4.3.0 ⏵ 4.4.0
	cargo/​uuid@​1.23.1 ⏵ 1.23.4
	cargo/​syn@​2.0.117 ⏵ 2.0.118

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Recently published: cargo arrayvec published 5 days ago Location: Package overview From: ? → cargo/solana-entry@3.1.12 → cargo/solana-runtime@3.1.12 → cargo/solana-accounts-db@3.1.12 → cargo/agave-snapshots@3.1.12 → cargo/solana-ledger@3.1.12 → cargo/jetstreamer-firehose@0.6.0 → cargo/sqlx@0.8.6 → cargo/solana-program@3.0.0 → cargo/solana-message@3.0.1 → cargo/arrayvec@0.7.7 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/arrayvec@0.7.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo auto_enums published 7 days ago Location: Package overview From: ? → cargo/juniper@0.16.2 → cargo/auto_enums@0.8.9 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/auto_enums@0.8.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo bitvec published 7 days ago Location: Package overview From: ? → cargo/solana-entry@3.1.12 → cargo/solana-runtime@3.1.12 → cargo/solana-ledger@3.1.12 → cargo/jetstreamer-firehose@0.6.0 → cargo/sqlx@0.8.6 → cargo/solana-program@3.0.0 → cargo/bitvec@1.1.1 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/bitvec@1.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo borsh-derive published 7 days ago Location: Package overview From: ? → cargo/borsh@1.7.0 → cargo/borsh-derive@1.7.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/borsh-derive@1.7.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo borsh published 7 days ago Location: Package overview From: Cargo.lock → cargo/borsh@1.7.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/borsh@1.7.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo bstr published 1 hour ago Location: Package overview From: ? → cargo/jetstreamer-firehose@0.6.0 → cargo/bstr@1.12.3 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/bstr@1.12.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo cc published 6 days ago Location: Package overview From: ? → cargo/reqwest@0.12.28 → cargo/solana-account-decoder-client-types@3.1.12 → cargo/solana-account-decoder@3.1.12 → cargo/solana-entry@3.1.12 → cargo/solana-client@3.1.12 → cargo/solana-runtime@3.1.12 → cargo/solana-accounts-db@3.1.12 → cargo/agave-snapshots@3.1.12 → cargo/solana-ledger@3.1.12 → cargo/jetstreamer-firehose@0.6.0 → cargo/tonic@0.14.6 → cargo/reqwest@0.13.4 → cargo/chrono@0.4.45 → cargo/rustls@0.23.41 → cargo/tonic@0.9.2 → cargo/protobuf-src@1.1.0%2B21.5 → cargo/reqwest@0.11.27 → cargo/solana-program@3.0.0 → cargo/solana-message@3.0.1 → cargo/cc@1.2.65 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/cc@1.2.65. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo env_filter published 1 hour ago Location: Package overview From: ? → cargo/env_logger@0.11.11 → cargo/env_filter@2.0.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/env_filter@2.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo env_logger published 1 hour ago Location: Package overview From: Cargo.lock → cargo/env_logger@0.11.11 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/env_logger@0.11.11. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo jiff-static published 5 days ago Location: Package overview From: ? → cargo/env_logger@0.11.11 → cargo/jiff-static@0.2.29 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/jiff-static@0.2.29. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo jiff published 5 days ago Location: Package overview From: ? → cargo/env_logger@0.11.11 → cargo/jiff@0.2.29 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/jiff@0.2.29. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo js-sys published 19 hours ago Location: Package overview From: ? → cargo/reqwest@0.12.28 → cargo/solana-account@3.4.0 → cargo/spl-type-length-value@0.9.1 → cargo/spl-pod@0.7.3 → cargo/solana-transaction-context@3.1.12 → cargo/solana-account-decoder-client-types@3.1.12 → cargo/solana-account-decoder@3.1.12 → cargo/solana-transaction-status@3.1.12 → cargo/solana-entry@3.1.12 → cargo/solana-client@3.1.12 → cargo/solana-runtime@3.1.12 → cargo/solana-accounts-db@3.1.12 → cargo/agave-snapshots@3.1.12 → cargo/solana-ledger@3.1.12 → cargo/solana-genesis-utils@3.1.12 → cargo/solana-pubkey@4.2.0 → cargo/jetstreamer-firehose@0.6.0 → cargo/tonic@0.14.6 → cargo/reqwest@0.13.4 → cargo/chrono@0.4.45 → cargo/rustls@0.23.41 → cargo/uuid@1.23.4 → cargo/tonic@0.13.1 → cargo/sqlx@0.8.6 → cargo/tonic@0.9.2 → cargo/axum@0.6.20 → cargo/protobuf-src@1.1.0%2B21.5 → cargo/reqwest@0.11.27 → cargo/metrics-exporter-prometheus@0.16.2 → cargo/solana-program@3.0.0 → cargo/solana-pubkey@3.0.0 → cargo/solana-clock@3.0.0 → cargo/spl-token-group-interface@0.7.1 → cargo/spl-token-interface@2.0.0 → cargo/spl-token-metadata-interface@0.8.0 → cargo/solana-signature@3.1.0 → cargo/solana-message@3.0.1 → cargo/spl-token-2022@10.0.0 → cargo/solana-system-interface@3.0.0 → cargo/solana-transaction@3.0.2 → cargo/js-sys@0.3.103 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/js-sys@0.3.103. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo log published 5 days ago Location: Package overview From: Cargo.lock → cargo/log@0.4.33 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/log@0.4.33. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo memmap2 published 3 days ago Location: Package overview From: ? → cargo/solana-runtime@3.1.12 → cargo/solana-accounts-db@3.1.12 → cargo/memmap2@0.9.11 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/memmap2@0.9.11. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo quinn-proto published 3 days ago Location: Package overview From: ? → cargo/reqwest@0.12.28 → cargo/reqwest@0.13.4 → cargo/quinn-proto@0.11.15 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/quinn-proto@0.11.15. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo quinn published 3 days ago Location: Package overview From: ? → cargo/reqwest@0.12.28 → cargo/reqwest@0.13.4 → cargo/quinn@0.11.11 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/quinn@0.11.11. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo quote published 3 days ago Location: Package overview From: Cargo.lock → cargo/quote@1.0.46 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/quote@1.0.46. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo rustls published 3 days ago Location: Package overview From: Cargo.lock → cargo/rustls@0.23.41 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/rustls@0.23.41. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo solana-epoch-rewards published 22 hours ago Location: Package overview From: ? → cargo/solana-account@3.4.0 → cargo/solana-account-decoder@3.1.12 → cargo/solana-transaction-status@3.1.12 → cargo/solana-entry@3.1.12 → cargo/solana-runtime@3.1.12 → cargo/solana-accounts-db@3.1.12 → cargo/solana-ledger@3.1.12 → cargo/jetstreamer-firehose@0.6.0 → cargo/solana-program@3.0.0 → cargo/spl-token-2022@10.0.0 → cargo/solana-epoch-rewards@3.1.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/solana-epoch-rewards@3.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo solana-get-sysvar published 2 days ago Location: Package overview From: ? → cargo/solana-account@3.4.0 → cargo/solana-account-decoder@3.1.12 → cargo/solana-transaction-status@3.1.12 → cargo/solana-entry@3.1.12 → cargo/solana-runtime@3.1.12 → cargo/solana-accounts-db@3.1.12 → cargo/solana-ledger@3.1.12 → cargo/jetstreamer-firehose@0.6.0 → cargo/solana-program@3.0.0 → cargo/spl-token-2022@10.0.0 → cargo/solana-get-sysvar@1.0.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/solana-get-sysvar@1.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo solana-instruction-error published 5 hours ago Location: Package overview From: ? → cargo/solana-account@3.4.0 → cargo/spl-pod@0.7.3 → cargo/solana-transaction-context@3.1.12 → cargo/solana-transaction-status-client-types@3.1.12 → cargo/solana-account-decoder@3.1.12 → cargo/solana-transaction-status@3.1.12 → cargo/solana-entry@3.1.12 → cargo/solana-client@3.1.12 → cargo/solana-runtime@3.1.12 → cargo/solana-accounts-db@3.1.12 → cargo/agave-snapshots@3.1.12 → cargo/solana-ledger@3.1.12 → cargo/solana-genesis-utils@3.1.12 → cargo/jetstreamer-firehose@0.6.0 → cargo/solana-program@3.0.0 → cargo/solana-instruction@3.0.0 → cargo/solana-message@3.0.1 → cargo/yellowstone-grpc-proto@10.1.1 → cargo/spl-token-2022@10.0.0 → cargo/solana-transaction@3.0.2 → cargo/solana-instruction-error@2.4.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/solana-instruction-error@2.4.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo solana-last-restart-slot published 22 hours ago Location: Package overview From: ? → cargo/solana-account@3.4.0 → cargo/solana-account-decoder@3.1.12 → cargo/solana-transaction-status@3.1.12 → cargo/solana-entry@3.1.12 → cargo/solana-runtime@3.1.12 → cargo/solana-accounts-db@3.1.12 → cargo/solana-ledger@3.1.12 → cargo/jetstreamer-firehose@0.6.0 → cargo/solana-program@3.0.0 → cargo/spl-token-2022@10.0.0 → cargo/solana-last-restart-slot@3.1.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/solana-last-restart-slot@3.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo solana-rent published 22 hours ago Location: Package overview From: ? → cargo/solana-client@3.1.12 → cargo/solana-runtime@3.1.12 → cargo/solana-genesis-utils@3.1.12 → cargo/jetstreamer-firehose@0.6.0 → cargo/solana-rent@4.3.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/solana-rent@4.3.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo solana-slot-hashes published 22 hours ago Location: Package overview From: ? → cargo/solana-account@3.4.0 → cargo/solana-account-decoder@3.1.12 → cargo/solana-transaction-status@3.1.12 → cargo/solana-entry@3.1.12 → cargo/solana-runtime@3.1.12 → cargo/solana-accounts-db@3.1.12 → cargo/solana-ledger@3.1.12 → cargo/jetstreamer-firehose@0.6.0 → cargo/solana-program@3.0.0 → cargo/spl-token-2022@10.0.0 → cargo/solana-slot-hashes@3.1.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/solana-slot-hashes@3.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Recently published: cargo solana-slot-history published 22 hours ago Location: Package overview From: ? → cargo/solana-account@3.4.0 → cargo/solana-account-decoder@3.1.12 → cargo/solana-transaction-status@3.1.12 → cargo/solana-entry@3.1.12 → cargo/solana-runtime@3.1.12 → cargo/solana-accounts-db@3.1.12 → cargo/solana-ledger@3.1.12 → cargo/jetstreamer-firehose@0.6.0 → cargo/solana-program@3.0.0 → cargo/spl-token-2022@10.0.0 → cargo/solana-slot-history@3.1.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: 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@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/solana-slot-history@3.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
See 24 more rows in the dashboard

View full report