supply chain / pytest

pytest

registryPyPI
package namepytest
maintainerpytest Contributors

pytest is the standard test runner for Python, present in essentially every Python project with a test suite. It is typically installed in CI/CD pipelines and developer environments. pytest plugins can execute arbitrary code during test collection, before any test function runs.

api usage

Checking pytest

pytest 8.3.0 is a clean version with no known supply chain compromise. The response returns compromised: false with an empty sources array.

bash
curl "https://api.attestd.io/v1/check?product=pytest&version=8.3.0" \
  -H "Authorization: Bearer YOUR_API_KEY"
json
{
  "product": "pytest",
  "version": "8.3.0",
  "supported": true,
  "risk_state": "none",
  "supply_chain": {
    "compromised": false,
    "sources": [],
    "malware_type": null,
    "description": null,
    "advisory_url": null,
    "compromised_at": null,
    "removed_at": null
  },
  "last_updated": "2026-05-01T00:00:00Z"
}
attack surface

Why this package is monitored

Test runner packages execute during CI/CD pipelines that have access to deployment credentials, environment secrets, and cloud provider tokens. A compromised pytest version or plugin can exfiltrate CI environment variables during any test run.

Attestd monitors pytest using the following detection sources:

registry

Manually curated advisories in the Attestd registry, verified by a human analyst. Confidence 1.0.

osv

OSV.dev malicious-package advisories with IDs prefixed MAL-. Confidence 0.95.

pypi_yank

Versions yanked on PyPI with a security-related yanked_reason annotation. Confidence 0.80.

related