PyPI project pages now carry a Security tab with per-release provenance
The redesigned pages show whether a release has full provenance (every file attested via Trusted Publishing or SLSA build provenance), none, incomplete, inconsistent, a change of provenance, or a loss of it. A loss or change is the useful signal: it means a release came from a different repository or workflow than the last one, or stopped being attested. PyPI says a missing attestation is common on older releases and does not mean the file is malicious. If you publish to PyPI, moving to Trusted Publishing is now visible to every downstream reader.
Rust 1.100 stabilizes the never type and can report unused Cargo dependencies
Released Nov 12: the never type is stable, core parts of the Allocator API are stable, and Cargo can now report dependencies a project does not use. The LWN comments make the security point: an unused dependency can still ship a build.rs that runs on your build host, so deleting it removes that exposure along with the compile time.