$ the-wire · showcase
Pydantic documents how coordinated vulnerability response works for enterprise customers
By RepoJournal · Filed · About FastAPI & Pydantic · Composed from the cited sources · methodology
1 person shipped this
Pydantic's only shipped change in the last day is documentation: what an enterprise agreement adds to vulnerability handling, and what stays available to everyone.
Document coordinated vulnerability response in enterprise support (#13812) pydantic/pydantic
The commit documents coordinated vulnerability response for covered release lines, spelling out the named contacts and coordination an enterprise agreement adds. Private vulnerability reporting itself remains open to everyone, so users without a support contract lose nothing here.
Document coordinated vulnerability response in enterprise support pydantic/pydantic
The pull request summary says the docs cover impact assessment, mitigations, patched releases, advisories, CVEs, and disclosure, and that they were rendered through unified-docs in a production build and checked at desktop and mobile viewport widths. Nothing in the codebase changed.
