You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expiry automation: check the PGP key's expiry and warn ahead of lapse without calendar entries #133
The security contact material in .well-known/ has two expiry dates: the Expires field of security.txt (RFC 9116) and the validity of the PGP key in pgp-security.asc. Today only the first is checked (#109), and only by failing the next PR after it has already lapsed. Nothing checks the key, and nothing warns beforehand. Renewal currently depends on someone remembering, and the team does not want calendar entries for it: the repo should tell us.
Scope
A new validate check that reads the key in .well-known/pgp-security.asc and fails when the primary key, or any encryption/signing subkey, is expired, revoked, or cannot be parsed. Absent file is fine (fixture trees carry none).
A --horizon-days <n> option on npm run validate that makes both expiry checks (security.txt Expires, PGP key) fail when the date falls within the next n days. PR checks keep the default of 0, so ordinary PRs are not blocked by an upcoming expiry.
A scheduled workflow that runs the checks daily with a 5 day horizon and opens (or updates) a single labelled issue when one trips, closing it when renewed, so the warning arrives in the issue tracker.
CLAUDE.md updated to describe the new check and the watch.
Acceptance
Unit tests cover expired, revoked, unparseable, within-horizon, and healthy cases for the key check, and the horizon for security.txt.
The repo's own key and security.txt pass today.
The scheduled workflow can be triggered manually and does not create duplicate issues.
Activity
Run the expiry watch daily with a 5-day horizon (#133)
Merge pull request #134 from material-identity/feat/expiry-automation