Skip to content

Security: sara-czasak/py-simple-wrap

SECURITY.md

🏠README Β· ⚑Quickstart Β· πŸ“¦Modules Β· πŸ†˜Support Β· πŸš€Contributing Β· 🌟Contributors Β· πŸ“œChangelog Β· 🌱Code of Conduct Β· βš–οΈLicense

Security Policy πŸ”’

Supported Versions

py-simple-wrap is a young project and hasn't reached a stable 1.0 release yet, so there isn't a long history of versions to maintain in parallel. Only the latest published release on PyPI receives security fixes.

Version Supported
Latest release on PyPI βœ…
Any older release ❌

If you're on an older version, please upgrade to the latest release before reporting β€” there's a good chance it's already fixed.

Reporting a Vulnerability

Please do not open a public GitHub Issue for security vulnerabilities β€” that could expose the problem to others before it's fixed.

Instead, report it privately to the maintainer, @sara-czasak, using GitHub's private vulnerability reporting on this repo (Security tab β†’ "Report a vulnerability"). If that's not available for any reason, open a private message via GitHub instead.

When reporting, please include:

  • A description of the vulnerability and its potential impact
  • Steps to reproduce it (a minimal code snippet is ideal)
  • The version of py-simple-wrap you're using What to expect:
  • I'll acknowledge your report within 3–5 days.
  • I'll keep you updated on progress at least once a week while it's being investigated.
  • If the vulnerability is confirmed, I'll work on a fix and aim to release a patched version as quickly as possible, then credit you in the release notes (unless you'd rather stay anonymous).
  • If it's declined (e.g. not reproducible, or determined not to be a security issue), I'll explain why. Since this is a solo-maintained, beginner-focused project, response times may occasionally be a little slower than a large project's SLA β€” thank you in advance for your patience, and for helping keep Py_simple safe for the people learning from it. 🌱

There aren't any published security advisories