├── CODE_OF_CONDUCT.md ├── LICENSE-APACHE ├── LICENSE-MIT ├── README.md └── img └── safety-dance.png /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # The Rust Code of Conduct 2 | 3 | ## Conduct 4 | 5 | **Contact**: [Secure Code WG][wg] 6 | 7 | * We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic. 8 | * On IRC, please avoid using overtly sexual nicknames or other nicknames that might detract from a friendly, safe and welcoming environment for all. 9 | * Please be kind and courteous. There's no need to be mean or rude. 10 | * Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer. 11 | * Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works. 12 | * We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term "harassment" as including the definition in the [Citizen Code of Conduct](http://citizencodeofconduct.org/); if you have any lack of clarity about what might be included in that concept, please read their definition. In particular, we don't tolerate behavior that excludes people in socially marginalized groups. 13 | * Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact one of the channel ops or any of the [Secure Code WG][wg] immediately. Whether you're a regular contributor or a newcomer, we care about making this community a safe place for you and we've got your back. 14 | * Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome. 15 | 16 | ## Moderation 17 | 18 | 19 | These are the policies for upholding our community's standards of conduct. If you feel that a thread needs moderation, please contact the [Secure Code WG][wg]. 20 | 21 | 1. Remarks that violate the Rust standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hateful manner.) 22 | 2. Remarks that moderators find inappropriate, whether listed in the code of conduct or not, are also not allowed. 23 | 3. Moderators will first respond to such remarks with a warning. 24 | 4. If the warning is unheeded, the user will be "kicked," i.e., kicked out of the communication channel to cool off. 25 | 5. If the user comes back and continues to make trouble, they will be banned, i.e., indefinitely excluded. 26 | 6. Moderators may choose at their discretion to un-ban the user if it was a first offense and they offer the offended party a genuine apology. 27 | 7. If a moderator bans someone and you think it was unjustified, please take it up with that moderator, or with a different moderator, **in private**. Complaints about bans in-channel are not allowed. 28 | 8. Moderators are held to a higher standard than other community members. If a moderator creates an inappropriate situation, they should expect less leeway than others. 29 | 30 | In the Rust community we strive to go the extra step to look out for each other. Don't just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they're off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely. 31 | 32 | And if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could've communicated better — remember that it's your responsibility to make your fellow Rustaceans comfortable. Everyone wants to get along and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust. 33 | 34 | The enforcement policies listed above apply to all official Secure Code WG venues; including official instant messaging channels; and GitHub repositories under rust-secure-code. 35 | 36 | *Adapted from the [Node.js Policy on Trolling](http://blog.izs.me/post/30036893703/policy-on-trolling) as well as the [Contributor Covenant v1.3.0](https://www.contributor-covenant.org/version/1/3/0/).* 37 | 38 | [wg]: https://github.com/orgs/rust-secure-code/people 39 | -------------------------------------------------------------------------------- /LICENSE-APACHE: -------------------------------------------------------------------------------- 1 | 2 | Apache License 3 | Version 2.0, January 2004 4 | http://www.apache.org/licenses/ 5 | 6 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 7 | 8 | 1. Definitions. 9 | 10 | "License" shall mean the terms and conditions for use, reproduction, 11 | and distribution as defined by Sections 1 through 9 of this document. 12 | 13 | "Licensor" shall mean the copyright owner or entity authorized by 14 | the copyright owner that is granting the License. 15 | 16 | "Legal Entity" shall mean the union of the acting entity and all 17 | other entities that control, are controlled by, or are under common 18 | control with that entity. For the purposes of this definition, 19 | "control" means (i) the power, direct or indirect, to cause the 20 | direction or management of such entity, whether by contract or 21 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 22 | outstanding shares, or (iii) beneficial ownership of such entity. 23 | 24 | "You" (or "Your") shall mean an individual or Legal Entity 25 | exercising permissions granted by this License. 26 | 27 | "Source" form shall mean the preferred form for making modifications, 28 | including but not limited to software source code, documentation 29 | source, and configuration files. 30 | 31 | "Object" form shall mean any form resulting from mechanical 32 | transformation or translation of a Source form, including but 33 | not limited to compiled object code, generated documentation, 34 | and conversions to other media types. 35 | 36 | "Work" shall mean the work of authorship, whether in Source or 37 | Object form, made available under the License, as indicated by a 38 | copyright notice that is included in or attached to the work 39 | (an example is provided in the Appendix below). 40 | 41 | "Derivative Works" shall mean any work, whether in Source or Object 42 | form, that is based on (or derived from) the Work and for which the 43 | editorial revisions, annotations, elaborations, or other modifications 44 | represent, as a whole, an original work of authorship. For the purposes 45 | of this License, Derivative Works shall not include works that remain 46 | separable from, or merely link (or bind by name) to the interfaces of, 47 | the Work and Derivative Works thereof. 48 | 49 | "Contribution" shall mean any work of authorship, including 50 | the original version of the Work and any modifications or additions 51 | to that Work or Derivative Works thereof, that is intentionally 52 | submitted to Licensor for inclusion in the Work by the copyright owner 53 | or by an individual or Legal Entity authorized to submit on behalf of 54 | the copyright owner. For the purposes of this definition, "submitted" 55 | means any form of electronic, verbal, or written communication sent 56 | to the Licensor or its representatives, including but not limited to 57 | communication on electronic mailing lists, source code control systems, 58 | and issue tracking systems that are managed by, or on behalf of, the 59 | Licensor for the purpose of discussing and improving the Work, but 60 | excluding communication that is conspicuously marked or otherwise 61 | designated in writing by the copyright owner as "Not a Contribution." 62 | 63 | "Contributor" shall mean Licensor and any individual or Legal Entity 64 | on behalf of whom a Contribution has been received by Licensor and 65 | subsequently incorporated within the Work. 66 | 67 | 2. Grant of Copyright License. Subject to the terms and conditions of 68 | this License, each Contributor hereby grants to You a perpetual, 69 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 70 | copyright license to reproduce, prepare Derivative Works of, 71 | publicly display, publicly perform, sublicense, and distribute the 72 | Work and such Derivative Works in Source or Object form. 73 | 74 | 3. Grant of Patent License. Subject to the terms and conditions of 75 | this License, each Contributor hereby grants to You a perpetual, 76 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 77 | (except as stated in this section) patent license to make, have made, 78 | use, offer to sell, sell, import, and otherwise transfer the Work, 79 | where such license applies only to those patent claims licensable 80 | by such Contributor that are necessarily infringed by their 81 | Contribution(s) alone or by combination of their Contribution(s) 82 | with the Work to which such Contribution(s) was submitted. If You 83 | institute patent litigation against any entity (including a 84 | cross-claim or counterclaim in a lawsuit) alleging that the Work 85 | or a Contribution incorporated within the Work constitutes direct 86 | or contributory patent infringement, then any patent licenses 87 | granted to You under this License for that Work shall terminate 88 | as of the date such litigation is filed. 89 | 90 | 4. Redistribution. You may reproduce and distribute copies of the 91 | Work or Derivative Works thereof in any medium, with or without 92 | modifications, and in Source or Object form, provided that You 93 | meet the following conditions: 94 | 95 | (a) You must give any other recipients of the Work or 96 | Derivative Works a copy of this License; and 97 | 98 | (b) You must cause any modified files to carry prominent notices 99 | stating that You changed the files; and 100 | 101 | (c) You must retain, in the Source form of any Derivative Works 102 | that You distribute, all copyright, patent, trademark, and 103 | attribution notices from the Source form of the Work, 104 | excluding those notices that do not pertain to any part of 105 | the Derivative Works; and 106 | 107 | (d) If the Work includes a "NOTICE" text file as part of its 108 | distribution, then any Derivative Works that You distribute must 109 | include a readable copy of the attribution notices contained 110 | within such NOTICE file, excluding those notices that do not 111 | pertain to any part of the Derivative Works, in at least one 112 | of the following places: within a NOTICE text file distributed 113 | as part of the Derivative Works; within the Source form or 114 | documentation, if provided along with the Derivative Works; or, 115 | within a display generated by the Derivative Works, if and 116 | wherever such third-party notices normally appear. The contents 117 | of the NOTICE file are for informational purposes only and 118 | do not modify the License. You may add Your own attribution 119 | notices within Derivative Works that You distribute, alongside 120 | or as an addendum to the NOTICE text from the Work, provided 121 | that such additional attribution notices cannot be construed 122 | as modifying the License. 123 | 124 | You may add Your own copyright statement to Your modifications and 125 | may provide additional or different license terms and conditions 126 | for use, reproduction, or distribution of Your modifications, or 127 | for any such Derivative Works as a whole, provided Your use, 128 | reproduction, and distribution of the Work otherwise complies with 129 | the conditions stated in this License. 130 | 131 | 5. Submission of Contributions. Unless You explicitly state otherwise, 132 | any Contribution intentionally submitted for inclusion in the Work 133 | by You to the Licensor shall be under the terms and conditions of 134 | this License, without any additional terms or conditions. 135 | Notwithstanding the above, nothing herein shall supersede or modify 136 | the terms of any separate license agreement you may have executed 137 | with Licensor regarding such Contributions. 138 | 139 | 6. Trademarks. This License does not grant permission to use the trade 140 | names, trademarks, service marks, or product names of the Licensor, 141 | except as required for reasonable and customary use in describing the 142 | origin of the Work and reproducing the content of the NOTICE file. 143 | 144 | 7. Disclaimer of Warranty. Unless required by applicable law or 145 | agreed to in writing, Licensor provides the Work (and each 146 | Contributor provides its Contributions) on an "AS IS" BASIS, 147 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 148 | implied, including, without limitation, any warranties or conditions 149 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 150 | PARTICULAR PURPOSE. You are solely responsible for determining the 151 | appropriateness of using or redistributing the Work and assume any 152 | risks associated with Your exercise of permissions under this License. 153 | 154 | 8. Limitation of Liability. In no event and under no legal theory, 155 | whether in tort (including negligence), contract, or otherwise, 156 | unless required by applicable law (such as deliberate and grossly 157 | negligent acts) or agreed to in writing, shall any Contributor be 158 | liable to You for damages, including any direct, indirect, special, 159 | incidental, or consequential damages of any character arising as a 160 | result of this License or out of the use or inability to use the 161 | Work (including but not limited to damages for loss of goodwill, 162 | work stoppage, computer failure or malfunction, or any and all 163 | other commercial damages or losses), even if such Contributor 164 | has been advised of the possibility of such damages. 165 | 166 | 9. Accepting Warranty or Additional Liability. While redistributing 167 | the Work or Derivative Works thereof, You may choose to offer, 168 | and charge a fee for, acceptance of support, warranty, indemnity, 169 | or other liability obligations and/or rights consistent with this 170 | License. However, in accepting such obligations, You may act only 171 | on Your own behalf and on Your sole responsibility, not on behalf 172 | of any other Contributor, and only if You agree to indemnify, 173 | defend, and hold each Contributor harmless for any liability 174 | incurred by, or claims asserted against, such Contributor by reason 175 | of your accepting any such warranty or additional liability. 176 | 177 | END OF TERMS AND CONDITIONS 178 | 179 | APPENDIX: How to apply the Apache License to your work. 180 | 181 | To apply the Apache License to your work, attach the following 182 | boilerplate notice, with the fields enclosed by brackets "[]" 183 | replaced with your own identifying information. (Don't include 184 | the brackets!) The text should be enclosed in the appropriate 185 | comment syntax for the file format. We also recommend that a 186 | file or class name and description of purpose be included on the 187 | same "printed page" as the copyright notice for easier 188 | identification within third-party archives. 189 | 190 | Copyright [yyyy] [name of copyright owner] 191 | 192 | Licensed under the Apache License, Version 2.0 (the "License"); 193 | you may not use this file except in compliance with the License. 194 | You may obtain a copy of the License at 195 | 196 | http://www.apache.org/licenses/LICENSE-2.0 197 | 198 | Unless required by applicable law or agreed to in writing, software 199 | distributed under the License is distributed on an "AS IS" BASIS, 200 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 201 | See the License for the specific language governing permissions and 202 | limitations under the License. 203 | -------------------------------------------------------------------------------- /LICENSE-MIT: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2019 Rust Secure Code WG 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Rust Safety Dance 2 | 3 | 4 | 5 | ## About 6 | 7 | This is a place for people to communicate about auditing `unsafe` code in core 8 | Rust crates and replacing it with safe code where feasible. 9 | 10 | **Everyone is invited to participate!** 11 | 12 | You **do not** have to be an `unsafe` expert to help out. There's a lot of work 13 | to do just picking crates (ones with a lot of reverse-dependencies are best), 14 | and then sorting out where they use `unsafe` and why. If you think something 15 | isn't right just post it in the tracking issue and others can have a look and 16 | talk it out. 17 | 18 | ## Process 19 | 20 | Our process is as follows: 21 | 22 | 1) File a tracking issue _in this repo_ about a particular crate, giving its 23 | name and a link to their github (or other repository location). 24 | 2) Audit `unsafe` usage in that crate. 25 | * This is easy to start! Note that the GitHub search isn't very good, so it's 26 | best to clone the project and use an editor on your own computer. The 27 | [cargo geiger](https://github.com/anderejd/cargo-geiger) command can also 28 | help here. 29 | * Once you know where the `unsafe` blocks are it gets harder: you have to 30 | carefully determine if the `unsafe` is being used appropriately. We've been 31 | [requesting Clippy lints](https://github.com/rust-secure-code/safety-dance/issues/21) 32 | for known antipatterns, so running `cargo +nightly clippy` is a good 33 | starting point. If you don't know if a certain `unsafe` block is okay, 34 | post the questionable block in a comment in the tracking issue here 35 | and someone else can have a look too, or ask in 36 | `#black-magic` on [Rust Community Discord](https://discord.gg/aVESxV8). 37 | 3) When problems are found with an `unsafe` block we want to file bug reports in 38 | that crate's repo, send PRs with fixes if possible, and also write up 39 | [security advisories](https://github.com/RustSec/advisory-db) if necessary. 40 | * If the `unsafe` block is sound, but can be converted to safe code without 41 | losing performance, that's a great thing to do! This is often the case 42 | thanks to Rust adding new safe abstractions and improving the optimizer 43 | since the code was originally written. 44 | * It's possible that `unsafe` can't be eliminated without a performance 45 | loss. Unfortunate, but it will happen some of the time. Note that benchmarks 46 | _must_ actually be used to back up any performance loss claims. There are 47 | already many cases where switching from `unsafe` to safe alternatives has 48 | _increased_ performance, so simply guessing that performance will regress 49 | is not enough. 50 | * If switching away from unsafe is impossible because of missing abstractions 51 | then that's important to know! We can work on improving the language, the 52 | standard library, and/or the crates.io ecosystem until the necessary gaps 53 | are filled in. 54 | 4) Once a crate has been gone over enough we close that issue. If the crate 55 | needs re-checking again later on we just open a new issue. 56 | 5) (Optional) If you have completely cleansed a crate of `unsafe`, add a 57 | `#![forbid(unsafe_code)]` attribute to its `src/lib.rs` or `main.rs`. 58 | After doing that, help others discover Safety Dance by adding a badge to 59 | your README.md: ![unsafe forbidden](https://img.shields.io/badge/unsafe-forbidden-success.svg) 60 | 61 | Markdown code: 62 | 63 | ``` 64 | [![unsafe forbidden](https://img.shields.io/badge/unsafe-forbidden-success.svg)](https://github.com/rust-secure-code/safety-dance/) 65 | ``` 66 | 67 | ## 🏆 Trophy Case 🏆 68 | 69 | Check out the safety improvements already done! 70 | 71 | ### [gif](https://crates.io/crates/gif) 72 | 73 | GIF image encoder/decoder written in Rust ([tracking issue](https://github.com/rust-secure-code/safety-dance/issues/24)) 74 | 75 | - Unsafe blocks before: **6** (ignoring C API) 76 | - Unsafe blocks after: **2** (ignoring C API) 77 | 78 | 100% safety blocked by [Polonius integration in rustc](https://github.com/rust-lang/rust/issues/51545) 79 | 80 | Done by: [Shnatsel](https://github.com/Shnatsel/) 81 | 82 | ### [flate2](https://crates.io/crates/flate2) 83 | 84 | A streaming compression/decompression library DEFLATE-based streams in Rust. Has C and Rust backends ([tracking issue](https://github.com/rust-secure-code/safety-dance/issues/32)) 85 | 86 | - Unsafe blocks before: **21** (when using Rust backend) 87 | - Unsafe blocks after: **2** (when using Rust backend) 88 | - Switched to using Rust backend by default (see [miniz_oxide](#miniz_oxide) below) 89 | 90 | Done by: [oyvindln](https://github.com/oyvindln/), [Shnatsel](https://github.com/Shnatsel/), [Alex Crichton](https://github.com/alexcrichton) 91 | 92 | ### [http](https://crates.io/crates/http) 93 | 94 | A general purpose library of common HTTP types ([tracking issue](https://github.com/rust-secure-code/safety-dance/issues/37)) 95 | 96 | - **Security bugs fixed: [RUSTSEC-2019-0033](https://rustsec.org/advisories/RUSTSEC-2019-0033.html), [RUSTSEC-2019-0034](https://rustsec.org/advisories/RUSTSEC-2019-0034.html)** 97 | 98 | Done by: [Qwaz](https://github.com/Qwaz), [Sean McArthur](https://github.com/seanmonstar) 99 | 100 | ### [image](https://crates.io/crates/image) 101 | 102 | Image operations and conversions to/from image formats ([tracking issue](https://github.com/rust-secure-code/safety-dance/issues/3)) 103 | 104 | - Unsafe blocks before: **21** (many of them unsound) 105 | - Unsafe blocks after: **6** 106 | - **Security bug fixed: [RUSTSEC-2019-0014](https://rustsec.org/advisories/RUSTSEC-2019-0014.html)** 107 | 108 | The remaining unsafe blocks are inherent and cannot be removed. They have been audited and found to be sound. 109 | 110 | Done by: [fintelia](https://github.com/fintelia), [HeroicKatora](https://github.com/HeroicKatora), [64](https://github.com/64) 111 | 112 | ### [libflate](https://crates.io/crates/libflate) 113 | 114 | Popular DEFLATE compression/decompression library ([tracking issue](https://github.com/rust-secure-code/safety-dance/issues/1)) 115 | 116 | - Unsafe blocks before: **16** (4 of them unsound) 117 | - Unsafe blocks after: **0** plus 2 moved to shared crates 118 | - **Security bug fixed: [RUSTSEC-2019-0010](https://rustsec.org/advisories/RUSTSEC-2019-0010.html)** 119 | 120 | Done by: [DevQps](https://github.com/DevQps), [Shnatsel](https://github.com/Shnatsel), [WanzenBug](https://github.com/WanzenBug), [mleonhard](https://github.com/mleonhard) 121 | 122 | ### [miniz_oxide](https://crates.io/crates/miniz_oxide) 123 | 124 | The fastest DEFLATE compression/decompression library in Rust, backend for [flate2](https://crates.io/crates/flate2) ([tracking issue](https://github.com/rust-secure-code/safety-dance/issues/2)) 125 | 126 | - Unsafe blocks before: **28** (2 of them unsound) 127 | - **100% safe code now** - while being faster than the C version! 128 | - Potential security issue fixed: [Frommi/miniz_oxide#36](https://github.com/Frommi/miniz_oxide/pull/36) (unclear if exploitable or not) 129 | 130 | Done by: [Shnatsel](https://github.com/Shnatsel/), [oyvindln](https://github.com/oyvindln/) 131 | 132 | ### [qbsdiff](https://crates.io/crates/qbsdiff) 133 | 134 | Fast and memory saving bsdiff 4.x compatible delta compressor and patcher ([tracking issue](https://github.com/rust-secure-code/safety-dance/issues/55)) 135 | 136 | - Unsafe blocks before: **3** 137 | - **100% safe code now** 138 | 139 | Done by: [Nicolas Braud-Santoni](https://github.com/nbraud) 140 | 141 | ### [spin](https://crates.io/crates/spin) 142 | 143 | A spinlock for Rust ([tracking issue](https://github.com/rust-secure-code/safety-dance/issues/18)) 144 | 145 | - `spin::RwLock` found to be unsound,completely rewritten based on Facebook's [Folly](https://github.com/facebook/folly) implementation, new implementation audited for soundness 146 | - **Security bug fixed: [RUSTSEC-2019-0013](https://rustsec.org/advisories/RUSTSEC-2019-0013.html)** 147 | - Unsafe code in `spin::Once` audited and found sound as of version 0.5.2 148 | 149 | Done by: [Matt Taylor](https://github.com/64), [Acrimon](https://github.com/xacrimon) 150 | 151 | ### [suffix-array](https://crates.io/crates/suffix_array) 152 | 153 | Suffix array construction and searching algorithms for in-memory binary data ([tracking issue](https://github.com/rust-secure-code/safety-dance/issues/56)) 154 | 155 | - Unsafe blocks before: **2** 156 | - **100% safe code now** 157 | 158 | Done by: [Nicolas Braud-Santoni](https://github.com/nbraud) 159 | 160 | ## We need your help! 161 | 162 | You can help by: 163 | 164 | 1. Nominating crates for auditing - we're looking for widely used crates with `unsafe` in them 165 | 1. Auditing nominated crates for soundness 166 | 1. Replacing unsafe code with safe code where possible (where not possible - documenting why) 167 | 1. Inspecting crates that have been made safer and [requesting Clippy lints](https://github.com/rust-secure-code/safety-dance/issues/21) for the antipatterns discovered 168 | 169 | Check out what's in progress or pick up a work item on the [issue tracker](https://github.com/rust-secure-code/safety-dance/issues)! 170 | -------------------------------------------------------------------------------- /img/safety-dance.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/rust-secure-code/safety-dance/096daa4cc6a45239ff2651394ae92d34eb615562/img/safety-dance.png --------------------------------------------------------------------------------