{"categories":[{"label":"Cryptography","url":"https://skillfed.io/packages/category/security-cryptography"}],"enrichment":{"capability":"Implements RFC 3161 Time-Stamp Protocol to build timestamp requests and verify timestamp responses using cryptographic certificates.","skillfed_tags":["cryptography","timestamp-protocol","rfc-3161"],"use_cases":["Build RFC 3161 timestamp requests to submit to a Time-Stamp Authority server for non-repudiation proof.","Verify timestamp responses from TSAs against trusted root certificates to validate authenticity.","Add cryptographic timestamping to document signing workflows to prove when a document existed.","Validate the authenticity of timestamped data by verifying the TSA's signature chain.","Integrate timestamping into compliance or audit logging systems requiring proof of time."],"what_it_does":"rfc3161-client is a Python library that implements the Time-Stamp Protocol (TSP) from RFC 3161, enabling you to create timestamp requests and verify timestamp responses from Time-Stamp Authorities (TSAs). The library is built on Rust bindings (via PyO3) for performance and correctness, wrapping ASN.1 encoding/decoding and cryptographic operations. It depends on cryptography for certificate handling.\n\nThe library provides two main workflows: building a timestamp request to send to a TSA server (which you must handle via your own HTTP client), and verifying the returned timestamp response against a set of trusted root certificates. It does not perform network activity itself\u2014you control how requests are sent and responses are fetched. This design keeps the library focused on protocol correctness rather than network concerns.","worth_installing":"Yes. The library is actively maintained, production-stable, has no known vulnerabilities, and solves a specific RFC 3161 compliance need. The permissive Apache 2.0 license and broad platform support (cp39-abi3 wheels) make adoption straightforward. Medium install friction is acceptable for a specialized cryptographic tool. Install if you need RFC 3161 timestamping; skip if you don't need protocol-compliant timestamp verification."},"id":"rfc3161-client","links":{"html":"https://skillfed.io/packages/rfc3161-client","md":"https://skillfed.io/packages/rfc3161-client.md","pypi":"https://pypi.org/project/rfc3161-client/"},"maintenance":{"status":"active"},"meta":{"latest_release":"2026-07-29","license_spdx":null,"license_treatment":"permissive","name":"rfc3161-client","python_support":"supports_current","summary":null},"popularity":{"monthly_downloads":899290,"position":4778,"tier":"top_5000"},"security":{"n_vulnerabilities":0},"version":"1.0.8"}