signxml-references-modified 1.0.0__tar.gz

signxml-references-modified-1.0.0/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {yyyy} {name of copyright owner}
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

signxml-references-modified-1.0.0/MANIFEST.in

@@ -0,0 +1,2 @@
+include signxml/schemas/*.xsd
+include signxml/xades/schemas/*.xsd

signxml-references-modified-1.0.0/NOTICE

@@ -0,0 +1,5 @@
+SignXML is a free open source implementation of the XML Signature and XAdES standards. The SignXML project is staffed by
+volunteers. If you are using this library in a for-profit project, please contribute to SignXML development and
+maintenance using the "Sponsor" button on the SignXML GitHub project page, https://github.com/XML-Security/signxml. If
+you are looking for support with your commercial XML Signature or XAdES based application, please donate and contact
+SignXML developers using the issue tracker on the SignXML project page or the contact information listed in README.rst.

signxml-references-modified-1.0.0/PKG-INFO

@@ -0,0 +1,287 @@
+Metadata-Version: 2.1
+Name: signxml-references-modified
+Version: 1.0.0
+Summary: Python XML Signature and XAdES library
+Home-page: https://github.com/deisymo/signxml
+Author: Andrey Kislyuk
+Author-email: kislyuk@gmail.com
+License: Apache Software License
+Platform: MacOS X
+Platform: Posix
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: MacOS :: MacOS X
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3.7
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.7
+Provides-Extra: tests
+License-File: LICENSE
+License-File: NOTICE
+
+SignXML: XML Signature and XAdES in Python
+==========================================
+
+*SignXML* is an implementation of the W3C `XML Signature <http://en.wikipedia.org/wiki/XML_Signature>`_ standard in
+Python. This standard (also known as "XMLDSig") is used to provide payload security in `SAML 2.0
+<http://en.wikipedia.org/wiki/SAML_2.0>`_, `XAdES <https://en.wikipedia.org/wiki/XAdES>`_, `EBICS
+<https://en.wikipedia.org/wiki/Electronic_Banking_Internet_Communication_Standard>`_, and `WS-Security
+<https://en.wikipedia.org/wiki/WS-Security>`_, among other uses. The standard is defined in the `W3C Recommendation
+<https://www.w3.org/standards/types#REC>`_ `XML Signature Syntax and Processing Version 1.1
+<http://www.w3.org/TR/xmldsig-core1/>`_. *SignXML* implements all of the required components of the Version 1.1
+standard, and most recommended ones. Its features are:
+
+* Use of a libxml2-based XML parser configured to defend against
+  `common XML attacks <https://docs.python.org/3/library/xml.html#xml-vulnerabilities>`_ when verifying signatures
+* Extensions to allow signing with and verifying X.509 certificate chains, including hostname/CN validation
+* Extensions to sign and verify `XAdES <https://en.wikipedia.org/wiki/XAdES>`_ signatures
+* Support for exclusive XML canonicalization with inclusive prefixes (`InclusiveNamespaces PrefixList
+  <http://www.w3.org/TR/xml-exc-c14n/#def-InclusiveNamespaces-PrefixList>`_, required to verify signatures generated by
+  some SAML implementations)
+* Modern Python compatibility (3.7-3.11+ and PyPy)
+* Well-supported, portable, reliable dependencies: `lxml <https://github.com/lxml/lxml>`_ and
+  `cryptography <https://github.com/pyca/cryptography>`_
+* Comprehensive testing (including the XMLDSig interoperability suite) and `continuous integration
+  <https://github.com/XML-Security/signxml/actions>`_
+* Simple interface with useful, ergonomic, and secure defaults (no network calls, XSLT or XPath transforms)
+* Compactness, readability, and extensibility
+
+Installation
+------------
+::
+
+    pip install signxml
+
+Synopsis
+--------
+SignXML uses the `lxml ElementTree API <https://lxml.de/tutorial.html>`_ to work with XML data.
+
+.. code-block:: python
+
+    from lxml import etree
+    from signxml import XMLSigner, XMLVerifier
+
+    data_to_sign = "<Test/>"
+    cert = open("cert.pem").read()
+    key = open("privkey.pem").read()
+    root = etree.fromstring(data_to_sign)
+    signed_root = XMLSigner().sign(root, key=key, cert=cert)
+    verified_data = XMLVerifier().verify(signed_root).signed_xml
+
+To make this example self-sufficient for test purposes:
+
+- Generate a test certificate and key using
+  ``openssl req -x509 -nodes -subj "/CN=test" -days 1 -newkey rsa -keyout privkey.pem -out cert.pem``
+  (run ``apt-get install openssl``, ``yum install openssl``, or ``brew install openssl`` if the ``openssl`` executable
+  is not found).
+- Pass the ``x509_cert=cert`` keyword argument to ``XMLVerifier.verify()``. (In production, ensure this is replaced with
+  the correct configuration for the trusted CA or certificate - this determines which signatures your application
+  trusts.)
+
+.. _verifying-saml-assertions:
+
+Verifying SAML assertions
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Assuming ``metadata.xml`` contains SAML metadata for the assertion source:
+
+.. code-block:: python
+
+    from lxml import etree
+    from base64 import b64decode
+    from signxml import XMLVerifier
+
+    with open("metadata.xml", "rb") as fh:
+        cert = etree.parse(fh).find("//ds:X509Certificate").text
+
+    assertion_data = XMLVerifier().verify(b64decode(assertion_body), x509_cert=cert).signed_xml
+
+.. admonition:: Signing SAML assertions
+
+ The SAML assertion schema specifies a location for the enveloped XML signature (between ``<Issuer>`` and
+ ``<Subject>``). To sign a SAML assertion in a schema-compliant way, insert a signature placeholder tag at that location
+ before calling XMLSigner: ``<ds:Signature Id="placeholder"></ds:Signature>``.
+
+.. admonition:: See what is signed
+
+ It is important to understand and follow the best practice rule of "See what is signed" when verifying XML
+ signatures. The gist of this rule is: if your application neglects to verify that the information it trusts is
+ what was actually signed, the attacker can supply a valid signature but point you to malicious data that wasn't signed
+ by that signature. Failure to follow this rule can lead to vulnerability against attacks like
+ `SAML signature wrapping <https://www.usenix.org/system/files/conference/usenixsecurity12/sec12-final91.pdf>`_.
+
+ In SignXML, you can ensure that the information signed is what you expect to be signed by only trusting the
+ data returned by ``XMLVerifier.verify()``. The ``signed_xml`` attribute of the return value is the XML node or string
+ that was signed. We also recommend that you assert the expected location for the signature within the document:
+
+ .. code-block:: python
+
+    from signxml import XMLVerifier, SignatureConfiguration
+    config = SignatureConfiguration(location="./")
+    XMLVerifier(...).verify(..., expect_config=config)
+
+ **Recommended reading:** `W3C XML Signature Best Practices for Applications
+ <http://www.w3.org/TR/xmldsig-bestpractices/#practices-applications>`_, `On Breaking SAML: Be Whoever You Want to Be
+ <https://www.usenix.org/system/files/conference/usenixsecurity12/sec12-final91.pdf>`_, `Duo Finds SAML Vulnerabilities
+ Affecting Multiple Implementations <https://duo.com/blog/duo-finds-saml-vulnerabilities-affecting-multiple-implementations>`_
+
+.. admonition:: Establish trust
+
+ If you do not supply any keyword arguments to ``verify()``, the default behavior is to trust **any** valid XML
+ signature generated using a valid X.509 certificate trusted by your system's CA store. This means anyone can
+ get an SSL certificate and generate a signature that you will trust. To establish trust in the signer, use the
+ ``x509_cert`` argument to specify a certificate that was pre-shared out-of-band (e.g. via SAML metadata, as
+ shown in *Verifying SAML assertions*), or ``cert_subject_name`` to specify a
+ subject name that must be in the signing X.509 certificate given by the signature (verified as if it were a
+ domain name), or ``ca_pem_file`` to give a custom CA.
+
+XML signature construction methods: enveloped, detached, enveloping
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+The XML Signature specification defines three ways to compose a signature with the data being signed: enveloped,
+detached, and enveloping signature. Enveloped is the default method. To specify the type of signature that you want to
+generate, pass the ``method`` argument to ``sign()``:
+
+.. code-block:: python
+
+    signed_root = XMLSigner(method=signxml.methods.detached).sign(root, key=key, cert=cert)
+    verified_data = XMLVerifier().verify(signed_root).signed_xml
+
+For detached signatures, the code above will use the ``Id`` or ``ID`` attribute of ``root`` to generate a relative URI
+(``<Reference URI="#value"``). You can also override the value of ``URI`` by passing a ``reference_uri`` argument to
+``sign()``. To verify a detached signature that refers to an external entity, pass a callable resolver in
+``XMLVerifier().verify(data, uri_resolver=...)``.
+
+See the `API documentation <https://xml-security.github.io/signxml/#id5>`_ for more details.
+
+
+XML representation details: Configuring namespace prefixes and whitespace
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Some applications require a particular namespace prefix configuration - for example, a number of applications assume
+that the ``http://www.w3.org/2000/09/xmldsig#`` namespace is set as the default, unprefixed namespace instead of using
+the customary ``ds:`` prefix. While in normal use namespace prefix naming is an insignificant representation detail,
+it can be significant in some XML canonicalization and signature configurations. To configure the namespace prefix map
+when generating a signature, set the ``XMLSigner.namespaces`` attribute:
+
+.. code-block:: python
+
+    signer = signxml.XMLSigner(...)
+    signer.namespaces = {None: signxml.namespaces.ds}
+    signed_root = signer.sign(...)
+
+Similarly, whitespace in the signed document is significant for XML canonicalization and signature purposes. Do not
+pretty-print the XML after generating the signature, since this can unfortunately render the signature invalid.
+
+
+XML parsing security and compatibility with ``xml.etree.ElementTree``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+SignXML uses the `lxml <https://github.com/lxml/lxml>`_ ElementTree library, not the
+`ElementTree from Python's standard library <https://docs.python.org/3.8/library/xml.etree.elementtree.html>`_,
+to work with XML. lxml is used due to its superior resistance to XML attacks, as well as XML canonicalization and
+namespace organization features. It is recommended that you pass XML string input directly to signxml before further
+parsing, and use lxml to work with untrusted XML input in general. If you do pass ``xml.etree.ElementTree`` objects to
+SignXML, you should be aware of differences in XML namespace handling between the two libraries. See the following
+references for more information:
+
+* `How do I use lxml safely as a web-service endpoint?
+  <https://lxml.de/FAQ.html#how-do-i-use-lxml-safely-as-a-web-service-endpoint>`_
+* `ElementTree compatibility of lxml.etree <https://lxml.de/compatibility.html>`_
+* `XML Signatures with Python ElementTree <https://technotes.shemyak.com/posts/xml-signatures-with-python-elementtree>`_
+
+
+XAdES signatures
+~~~~~~~~~~~~~~~~
+`XAdES ("XML Advanced Electronic Signatures") <https://en.wikipedia.org/wiki/XAdES>`_ is a standard for attaching
+metadata to XML Signature objects. This standard is endorsed by the European Union as the implementation for its
+`eSignature <https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/eSignature+Overview>`_ regulations.
+
+SignXML supports signing and verifying documents using `XAdES <https://en.wikipedia.org/wiki/XAdES>`_ signatures:
+
+.. code-block:: python
+
+    from signxml import DigestAlgorithm
+    from signxml.xades import (XAdESSigner, XAdESVerifier, XAdESVerifyResult,
+                               XAdESSignaturePolicy, XAdESDataObjectFormat)
+    signature_policy = XAdESSignaturePolicy(
+        Identifier="MyPolicyIdentifier",
+        Description="Hello XAdES",
+        DigestMethod=DigestAlgorithm.SHA256,
+        DigestValue="Ohixl6upD6av8N7pEvDABhEL6hM=",
+    )
+    data_object_format = XAdESDataObjectFormat(
+        Description="My XAdES signature",
+        MimeType="text/xml",
+    )
+    signer = XAdESSigner(
+        signature_policy=signature_policy,
+        claimed_roles=["signer"],
+        data_object_format=data_object_format,
+        c14n_algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315",
+    )
+    signed_doc = signer.sign(doc, key=private_key, cert=certificate)
+
+.. code-block:: python
+
+    verifier = XAdESVerifier()
+    verify_results = verifier.verify(
+        signed_doc, x509_cert=certificate, expect_references=3, expect_signature_policy=signature_policy
+    )
+    for verify_result in verify_results:
+        if isinstance(verify_result, XAdESVerifyResult):
+            verify_result.signed_properties  # use this to access parsed XAdES properties
+
+Authors
+-------
+* `Andrey Kislyuk <https://github.com/kislyuk>`_ and SignXML contributors.
+
+Links
+-----
+* `Project home page (GitHub) <https://github.com/XML-Security/signxml>`_
+* `Documentation <https://xml-security.github.io/signxml/>`_
+* `Package distribution (PyPI) <https://pypi.python.org/pypi/signxml>`_
+* `Change log <https://github.com/XML-Security/signxml/blob/master/Changes.rst>`_
+* `List of W3C XML Signature standards and drafts <https://www.w3.org/TR/?title=xml%20signature>`_
+* `W3C Recommendation: XML Signature Syntax and Processing Version 1.1 <http://www.w3.org/TR/xmldsig-core1>`_
+* `W3C Working Group Note: XML Signature Best Practices <http://www.w3.org/TR/xmldsig-bestpractices/>`_
+* `XML-Signature Interoperability <http://www.w3.org/Signature/2001/04/05-xmldsig-interop.html>`_
+* `W3C Working Group Note: Test Cases for C14N 1.1 and XMLDSig Interoperability <http://www.w3.org/TR/xmldsig2ed-tests/>`_
+* `W3C Working Group Note: XML Signature Syntax and Processing Version 2.0 <http://www.w3.org/TR/xmldsig-core2>`_
+  (This draft standard proposal was never finalized and is not in general use.)
+* `Intelligence Community Technical Specification: Web Service Security Guidance for Use of XML Signature and XML
+  Encryption <https://github.com/XML-Security/signxml/blob/develop/docs/dni-guidance.pdf>`_
+* `XMLSec: Related links <https://www.aleksey.com/xmlsec/related.html>`_
+* `OWASP SAML Security Cheat Sheet <https://www.owasp.org/index.php/SAML_Security_Cheat_Sheet>`_
+* `Okta Developer Docs: SAML <https://developer.okta.com/standards/SAML/>`_
+
+Bugs
+~~~~
+Please report bugs, issues, feature requests, etc. on `GitHub <https://github.com/XML-Security/signxml/issues>`_.
+
+Versioning
+~~~~~~~~~~
+This package follows the `Semantic Versioning 2.0.0 <http://semver.org/>`_ standard. To control changes, it is
+recommended that application developers pin the package version and manage it using `pip-tools
+<https://github.com/jazzband/pip-tools>`_ or similar. For library developers, pinning the major version is
+recommended.
+
+License
+-------
+Copyright 2014-2024, Andrey Kislyuk and SignXML contributors. Licensed under the terms of the
+`Apache License, Version 2.0 <http://www.apache.org/licenses/LICENSE-2.0>`_. Distribution of the LICENSE and NOTICE
+files with source copies of this package and derivative works is **REQUIRED** as specified by the Apache License.
+
+.. image:: https://github.com/XML-Security/signxml/workflows/Test%20suite/badge.svg
+        :target: https://github.com/XML-Security/signxml/actions
+.. image:: https://codecov.io/github/XML-Security/signxml/coverage.svg?branch=master
+        :target: https://codecov.io/github/XML-Security/signxml?branch=master
+.. image:: https://img.shields.io/pypi/v/signxml.svg
+        :target: https://pypi.python.org/pypi/signxml
+.. image:: https://img.shields.io/pypi/l/signxml.svg
+        :target: https://pypi.python.org/pypi/signxml
+
+