a good rule of thumb (that i consistently struggle to not violate) is that any system that uses "policy" as a blanket term for delegating complexity to users is one that deserves extreme scrutiny
@inyourbits in the sense of making secure defaults harder; my experience is:
1. a tool/system comes with secure defaults 2. a user/demo needs a set of exceptions that are contextually reasonable/acceptable 3. the tool/system grows the ability to set "policies," and declaring a custom policy implicitly overrides *all* secure defaults instead of just the ones explicitly overridden
i think it's pretty interesting how "can a smartphone app handle 30s of internet connectivity, followed by 30s of non-connectivity, followed by 10s of connectivity" is still in 2024 a very strong proxy for "has the developer ever ridden the NYC subway"
i'm really excited to share the work my team at @trailofbits has been doing for the last year: Sigstore-based attestations are now live and generally available on PyPI!
if you're already using Trusted Publishing with the canonical pypi-publish action, you don't need to change anything: the action will generate and upload an attestation on your behalf.