python-nss-ng 1.1.0__tar.gz → 1.2.0__tar.gz

python_nss_ng-1.2.0/.git_archival.txt

@@ -0,0 +1,4 @@
+node: e6e197516189faac861f191a6a48f0e1d993ef3d
+node-date: 2026-06-12T13:13:22-06:00
+describe-name: v1.2.0
+ref-names: grafted, HEAD, tag: v1.2.0, origin/main, origin/HEAD

{python_nss_ng-1.1.0 → python_nss_ng-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-nss-ng
-Version: 1.1.0
+Version: 1.2.0
 Summary: Python bindings for Network Security Services (NSS) and Netscape Portable Runtime (NSPR)
 Keywords: nss,nspr,cryptography,ssl,tls,pki,x509,security
 Author-Email: John Dennis <jdennis@redhat.com>, Matthew Watkins <mwatkins@linuxfoundation.org>

python_nss_ng-1.2.0/SECURITY.md

@@ -0,0 +1,77 @@
+<!--
+SPDX-License-Identifier: Apache-2.0
+SPDX-FileCopyrightText: 2026 The Linux Foundation
+-->
+
+# Security Policy
+
+This document describes the security policy for this repository, including
+which versions receive security updates and how to report vulnerabilities.
+
+## Supported Versions
+
+Maintainers develop and merge security fixes on the default branch
+(`main`) and publish those fixes in the latest tagged release. Older
+releases and tags do not receive security updates. Users should track
+the latest tagged release for security patches.
+
+| Version               | Supported          |
+| --------------------- | ------------------ |
+| Latest tagged release | :white_check_mark: |
+| Older releases/tags   | :x:                |
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability in this project, please report it
+**privately** so that maintainers can investigate and release a fix before
+the issue becomes publicly known.
+
+### Preferred: GitHub Private Vulnerability Reporting
+
+Use GitHub's private vulnerability reporting feature:
+
+1. Navigate to the **Security** tab of this repository.
+2. Click **Report a vulnerability**.
+3. Provide as much detail as possible (see below).
+
+This creates a private advisory visible to maintainers.
+
+### Alternative: Email
+
+If you cannot use GitHub's private reporting, send an email to the Linux
+Foundation Release Engineering team at:
+
+- **<releng@linuxfoundation.org>**
+
+Please do **not** report security vulnerabilities through public GitHub
+issues, discussions, or pull requests.
+
+### What to Include
+
+To help maintainers triage and resolve the report, please include:
+
+- A clear description of the vulnerability and its potential impact.
+- Steps to reproduce the issue (proof-of-concept code or commands).
+- The affected version(s), commit SHA, or release tag.
+- Any known mitigations or workarounds.
+- Your name and contact details for follow-up (optional).
+
+## Response Process
+
+Maintainers will acknowledge receipt of vulnerability reports within
+**5 business days**. We aim to:
+
+1. Confirm the vulnerability and determine its severity.
+2. Develop and test a fix in a private branch or advisory.
+3. Coordinate a disclosure timeline with the reporter.
+4. Release a patched version and publish a security advisory.
+
+We follow a responsible disclosure process and credit reporters in the
+published advisory unless they request to remain anonymous.
+
+## Scope
+
+This policy covers the source code, configuration, and documentation
+in this repository. Please report vulnerabilities in upstream
+dependencies to their respective maintainers; this project will update
+affected dependencies once fixes become available.

python_nss_ng-1.2.0/_version.txt

@@ -0,0 +1 @@
+1.2.0

{python_nss_ng-1.1.0 → python_nss_ng-1.2.0}/pyproject.toml

@@ -319,3 +319,9 @@ before-all = "yum install -y nss-devel nspr-devel pkg-config || apt-get update &
 
 [tool.cibuildwheel.macos]
 before-all = "brew install nss nspr pkg-config"
+
+[tool.uv]
+# Supply-chain cooldown: do not resolve anything published in the last
+# 7 days (rolling window; uv records it as a relative span in uv.lock).
+# Requires uv >= 0.9.17 for the relative-duration ("7 days") form.
+exclude-newer = "7 days"

{python_nss_ng-1.1.0 → python_nss_ng-1.2.0}/uv.lock

@@ -9,6 +9,10 @@ resolution-markers = [
     "python_full_version < '3.12'",
 ]
 
+[options]
+exclude-newer = "0001-01-01T00:00:00Z" # This has no effect and is included for backwards compatibility when using relative exclude-newer values.
+exclude-newer-span = "P7D"
+
 [[package]]
 name = "ast-serialize"
 version = "0.3.0"

python_nss_ng-1.1.0/.git_archival.txt

@@ -1,4 +0,0 @@
-node: ceb747232755bf570e5ceacb4e3a82f5d31ca085
-node-date: 2026-06-09T07:15:24-06:00
-describe-name: v1.1.0
-ref-names: grafted, HEAD, tag: v1.1.0, origin/main, origin/HEAD

python_nss_ng-1.1.0/_version.txt

@@ -1 +0,0 @@
-1.1.0