A metadata and documentation patch. No runtime security behaviour changed.
Scanning, configuration review, runner review, scoring, schemas, finding IDs and the compatibility surface are all identical to 0.7.1. 0.7.1 remains functionally valid; 0.7.2 is the preferred current release because its distribution metadata and public documentation are fully corrected.
Why this release exists
PyPI stores a release description at upload time. The versionsec 0.7.1 description therefore permanently carries fifteen relative README links that resolve under pypi.org and return 404 — for example https://pypi.org/project/versionsec/MIGRATION.md. The README on main was already fixed, but a published description cannot be corrected in place and a released artifact must not be re-uploaded. This release is what delivers the fix.
Changes
- Documentation links in the long description are absolute canonical URLs.
docs/INTEGRATION_TESTING.mdnames the current wheel.tests/test_long_description_links.pylocks the README to portable links and checks the paths it references still exist. Structural, no network access.- Compatibility bridge
forgeguardmoves to 0.7.2 and pinsversionsec==0.7.2.
Verification
pytest 433 passed (426 + 7 new link tests)
migration tests 20 passed
subprocess release contract 23 passed
ruff check / format clean
twine check PASSED (wheel + sdist)
long-description links 27 total, 0 broken
Artifacts are the exact bytes qualified by the trusted push run; nothing was rebuilt for this release. Attestation verifies against this repository, and both a wrong-repository check and a single-byte mutation are correctly rejected.
SHA-256
ea7d40357d808ed490113a62b6dae7fe4af7e655b61c687c77689b4041828f5d versionsec-0.7.2-py3-none-any.whl
fcbacb335a17d43436c819507fdb968a12ff0754644ea6ee7e0e73fc5221b79d versionsec-0.7.2.tar.gz
The tag is an annotated, unsigned tag, the same as v0.7.1. No VersionSec signing identity exists on the release host and none was created for this run.