Skip to main content

digital-signature-governance-pack

PyPI version Downloads Hits Python versions License CI

GitHub repo

digital-signature-governance-pack is an SSOT Registry pack for digital-signature, advanced electronic signature, container, timestamping, validation, archival, and assurance-language governance.

It gives product, platform, and compliance teams a reusable ADR/SPEC starting point for repositories that need to govern PAdES, XAdES, CAdES, ASiC-S, ASiC-E, validation reports, timestamping, certificate and revocation handling, long-term archival evidence, and constrained eIDAS-facing claim language.

What Is An SSOT Registry Pack?

An SSOT Registry pack is an installable package of governed Architecture Decision Records (ADRs) and Specifications (SPECs) for ssot-registry. The pack supplies reusable decision and requirement documents that downstream repositories can synchronize into their local .ssot registry and link to features, tests, claims, evidence, and releases.

Why This Pack Exists

Digital-signature governance crosses technical standards, cryptographic evidence, validation semantics, archival policy, and assurance wording. Teams need one reviewed source for the decisions and requirements that shape signature-family support, timestamping, validation reports, certificate and revocation handling, long-term evidence, and regulated claim language.

This pack helps teams:

  • apply reviewed digital-signature governance requirements across projects
  • distinguish signature family, baseline level, container, validation, timestamping, and archival requirements
  • keep assurance and regulatory language tied to explicit evidence boundaries
  • give product, platform, compliance, and implementation teams stable ADR and SPEC IDs
  • connect downstream features, tests, claims, evidence, and releases to shared governance records

Domain Focus

The initial review surface is grounded in TrustSig's signature_and_container_standards_matrix.md and covers:

  • ETSI PAdES, XAdES, CAdES, and ASiC family standards
  • baseline levels B-B, B-T, B-LT, and B-LTA
  • PDF signature standards and ISO PDF extensions
  • W3C XML Signature and canonicalization surfaces
  • CMS, timestamping, PKIX, OCSP, ERS, XMLERS, and related RFCs
  • validation result and validation report modeling
  • cryptographic suite policy and algorithm allowlists
  • regulatory-language boundaries for eIDAS-related claims

Included ADRs

  • adr:0900 digital-signature standards targets are reviewed before governance inclusion

Included SPECs

  • spc:0900 digital-signature governance target review

Proposed ADR And SPEC Set

The first detailed proposal is documented in:

Digital Signature ADR/SPEC Proposal

The source standards matrix copied from TrustSig is available at:

Signature and Container Standards Matrix

Install With uv

Install the pack into a project environment:

uv add digital-signature-governance-pack

Install it alongside the SSOT Registry CLI:

uv add ssot-registry digital-signature-governance-pack

Run without adding dependencies to a project:

uvx --from ssot-registry --with digital-signature-governance-pack ssot --help

Install With The SSOT Registry Pack CLI

Pack-enabled SSOT Registry environments can install and synchronize packs through the pack command surface:

uvx --from ssot-registry ssot pack install digital-signature-governance-pack
uvx --from ssot-registry ssot pack sync . digital-signature-governance-pack

Use With The SSOT Registry CLI

After the pack is installed in the same environment as ssot-registry, synchronize ADRs and SPECs into a target repository:

uv run ssot adr sync .
uv run ssot spec sync .

Review the synchronized governance surface:

uv run ssot adr list .
uv run ssot spec list .
uv run ssot spec get . --id spc:0900

Use the IDs from this pack when linking project features, tests, claims, and release evidence in your local .ssot registry.

Programmatic Usage

from digital_signature_governance_pack import load_document_manifest, read_packaged_document_text

adr_manifest = load_document_manifest("adr")
spec_manifest = load_document_manifest("spec")

print(adr_manifest[0]["id"])
print(spec_manifest[0]["id"])

text = read_packaged_document_text("spec", "SPEC-0900-digital-signature-governance-target-review.yaml")
print(text[:120])

Resources

Metadata

Release files for digital-signature-governance-pack 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for digital-signature-governance-pack 0.1.3
File Size Uploaded
digital_signature_governance_pack-0.1.3.tar.gz 14.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for digital-signature-governance-pack 0.1.3
File Interpreter ABI Platform
digital_signature_governance_pack-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 27.8 kB

Release files / digital_signature_governance_pack-0.1.3.tar.gz

Download URL digital_signature_governance_pack-0.1.3.tar.gz
Size 14.2 kB
Tags Source
SHA-256 checksum
How to use checksums
0638546aefc51dfcbb5bbf3d3e7846c49e51992af15e70896824a4be0348fde4
BLAKE2b-256 checksum
How to use checksums
a813e2fb58c107f8c3540d4b8c9558800816abb9d9161d0a674d1ff9a5578dae
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.

Transparency log

Release files / digital_signature_governance_pack-0.1.3-py3-none-any.whl

Download URL digital_signature_governance_pack-0.1.3-py3-none-any.whl
Size 13.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f3508bf52afae29202f5211f3ca0b7535fb6febc9111ebaf7f39fd21c34f3d8e
BLAKE2b-256 checksum
How to use checksums
7e2386d41fa632a98ea9bbbc1f333e1d3c13ee621b09bb36db6eb692a43b784b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.3 This release

2 release files

0.1.2

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page