The usage of solana-security-txt previously recommended in the official usage guide has an issue:

When multiple projects within a build, including dependencies, define a security-txt, the build fails.

To avoid this issue, library authors - including projects that might be used as a library by others in the future - should exclude the security_txt macro during no-entrypoint builds.

Feel free to read up on the details in the issue on the security-txt repository.

The official usage guide has also been updated. This PR includes the recommended changes.

Running cargo +1.59.0 test --release and lots of tests fail. Any idea what could be the issue? Have you considered adding CI to this repo?

failures:
    compute_prepared_inputs_should_succeed
    deposit_should_succeed
    double_spend_should_not_succeed
    internal_transfer_should_succeed
    search_root_at_last_root_index_should_succeed
    signer_acc_not_in_first_place_should_not_succeed
    submit_proof_with_wrong_root_should_not_succeed
    submit_proof_with_wrong_signer_should_not_succeed
    withdrawal_should_succeed

Due to this error:

thread 'solana-bank-forks-client' panicked at 'Account data resizing not supported yet: 0 -> 4122. Consider making this test conditional on `#[cfg(feature = "test-bpf")]`', /Users/drew/.cargo/registry/src/github.com-1ecc6299db9ec823/solana-program-test-1.9.5/src/lib.rs:341:17
thread 'search_root_at_last_root_index_should_succeed' panicked at 'called `Result::unwrap()` on an `Err` value: IoError(Custom { kind: Other, error: "the request exceeded its deadline" })', tests/onchain.rs:2580:10