3 ms·
The title is a little misleading, and the results are at a glance a little alarming. If you base your definition of safe on whether you or your dependencies use
by onei 5y ago
The title is a little misleading, and the results are at a glance a little alarming. If you base your definition of safe on whether you or your dependencies use unsafe anywhere, then obviously you're going to find something of concern. However, if you measure the safety of your code line by line, then the results are much better. Similarly, there's a balance to be found when assuming unsafe code is unsound.
The question is ultimately a reminder to check your dependencies to make sure they're active and take reasonable steps for validating unsafe code.