extended_stats 0.1.0__tar.gz

extended_stats-0.1.0/.editorconfig

@@ -0,0 +1,37 @@
+# https://editorconfig.org
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+indent_style = space
+indent_size = 4
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.{html,css,js,json,sh,yml,yaml}]
+indent_size = 2
+
+[*.bat]
+indent_style = tab
+end_of_line = crlf
+
+[LICENSE]
+insert_final_newline = false
+
+[justfile]
+indent_style = space
+indent_size = 4
+
+# Ignore binary or generated files
+[*.{png,jpg,gif,ico,woff,woff2,ttf,eot,svg,pdf}]
+charset = unset
+end_of_line = unset
+indent_style = unset
+indent_size = unset
+trim_trailing_whitespace = unset
+insert_final_newline = unset
+max_line_length = unset
+
+[*.{diff,patch}]
+trim_trailing_whitespace = false

extended_stats-0.1.0/.gitignore

@@ -0,0 +1,60 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+build/
+dist/
+eggs/
+.eggs/
+*.egg-info/
+*.egg
+MANIFEST
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+coverage.xml
+.hypothesis/
+.pytest_cache/
+
+# Environments
+.env
+.envrc
+.venv
+
+# uv
+#   Generally recommended to include uv.lock in version control for
+#   reproducibility. Uncomment for libraries where you want consumers
+#   to resolve their own dependencies.
+# uv.lock
+
+# Ruff
+.ruff_cache/
+
+# Type checkers
+.mypy_cache/
+.dmypy.json
+dmypy.json
+.pyre/
+.pytype/
+
+# Documentation build output
+site/
+
+# IDE files
+# .idea/
+# .vscode/
+
+# GitHub 
+.github/
+
+# Containing files related to the README sections
+docs/

extended_stats-0.1.0/CHANGELOG/unreleased.md

@@ -0,0 +1,22 @@
+# Unreleased
+
+These are the changes that will go out in the next release.
+
+## Added
+
+Extended Statistics started out as a project generated from [Cookiecutter PyPackage](https://github.com/audreyfeldroy/cookiecutter-pypackage) containing:
+
+- Initial scaffold for Extended Statistics.
+- `src/extended_stats/` package with CLI (Typer + Rich), py.typed marker
+- Tests with pytest, coverage across Python 3.12/3.13/3.14
+- CI via GitHub Actions: lint (Ruff), type check (ty), test matrix, coverage reporting
+- Security scanning: CodeQL analysis for public repositories, Dependabot, and a Zizmor workflow audit
+- Docs site with Zensical + mkdocstrings and a GitHub Pages deployment workflow
+- Trusted publishing to PyPI with OIDC and build provenance attestation
+- `justfile` with dev commands: qa, test, type-check, docs-serve, release
+- Issue templates, PR template, contributing guide, code of conduct, security policy
+- MIT license, .editorconfig, .gitignore
+
+### Contributors
+
+[@dreireyez](https://github.com/dreireyez) (Djem Andreif Reyes) created Extended Statistics.

extended_stats-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,89 @@
+# Contributor Covenant 3.0
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, email contact.dafreyes@gmail.com.
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).

extended_stats-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,160 @@
+# Contributing
+
+Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
+
+You can contribute in many ways:
+
+## Types of Contributions
+
+### Report Bugs
+
+Report bugs at https://github.com/dreireyez/extended_stats/issues.
+
+If you are reporting a bug, please include:
+
+- Your operating system name and version.
+- Any details about your local setup that might be helpful in troubleshooting.
+- Detailed steps to reproduce the bug.
+
+### Fix Bugs
+
+Look through the GitHub issues for bugs. Anything tagged with "bug" and "help wanted" is open to whoever wants to implement it.
+
+### Implement Features
+
+Look through the GitHub issues for features. Anything tagged with "enhancement" and "help wanted" is open to whoever wants to implement it.
+
+### Write Documentation
+
+Extended Statistics could always use more documentation, whether as part of the official docs, in docstrings, or even on the web in blog posts, articles, and such.
+
+To preview the docs locally:
+
+```sh
+just docs-serve
+```
+
+This starts a local server at http://localhost:8000 with live reload. Edit
+files in `docs/` or add docstrings to your code (the API reference page is
+auto-generated). Run `just docs-build` to verify a production build.
+
+Docs deploy automatically on push to `main` after GitHub Pages is enabled. If
+the generator did not enable it, review the visibility implications first:
+[Pages sites can be public even when their repositories are private](https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site),
+and the feature may require a paid GitHub plan for private repositories. Then
+go to Settings > Pages, set the source to **GitHub Actions**, and enable the
+deployment workflow:
+
+```bash
+gh variable set DOCS_DEPLOYMENT_ENABLED \
+    --repo dreireyez/extended_stats \
+    --body true
+```
+
+Until then, deployment stays paused and local preview and builds still work.
+
+### Submit Feedback
+
+The best way to send feedback is to file an issue at https://github.com/dreireyez/extended_stats/issues.
+
+If you are proposing a feature:
+
+- Explain in detail how it would work.
+- Keep the scope as narrow as possible, to make it easier to implement.
+- Remember that this is a volunteer-driven project, and that contributions are welcome :)
+
+## Get Started!
+
+Ready to contribute? Here's how to set up extended_stats for local development.
+
+1. Fork the extended_stats repo on GitHub.
+2. Clone your fork locally:
+
+   ```sh
+   git clone git@github.com:your_name_here/extended_stats.git
+   ```
+
+3. Install your local copy with uv:
+
+   ```sh
+   cd extended_stats/
+   uv sync
+   ```
+
+4. Create a branch for local development:
+
+   ```sh
+   git checkout -b name-of-your-bugfix-or-feature
+   ```
+
+   Now you can make your changes locally.
+
+5. When you're done making changes, verify formatting, linting, types, and tests without modifying files:
+
+   ```sh
+   just check
+   ```
+
+   Use `just fix` to apply Ruff's automatic fixes, or `just fix-and-check` to apply them before verification.
+
+   Or run the tests alone:
+
+   ```sh
+   just test
+   ```
+
+6. Commit your changes and push your branch to GitHub:
+
+   ```sh
+   git add .
+   git commit -m "Your detailed description of your changes."
+   git push origin name-of-your-bugfix-or-feature
+   ```
+
+7. Submit a pull request through the GitHub website.
+
+## Pull Request Guidelines
+
+Before you submit a pull request, check that it meets these guidelines:
+
+1. The pull request should include tests.
+2. If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.md.
+3. The pull request should work for Python 3.12, 3.13, and 3.14. Tests run in GitHub Actions on every pull request to the main branch, make sure that the tests pass for all supported Python versions.
+
+## Tips
+
+To run a subset of tests:
+
+```sh
+uv run pytest tests/
+```
+
+## Releasing a New Version
+
+1. **Bump the version:**
+   ```bash
+   uv version <version>        # or: uv version --bump minor
+   ```
+2. **Commit:**
+   ```bash
+   git add pyproject.toml uv.lock
+   git commit -m "Bump version to <version>"
+   ```
+3. **Release:**
+   ```bash
+   just release
+   ```
+   This finalizes `CHANGELOG/unreleased.md` as
+   `CHANGELOG/<version>.md`, creates a fresh unreleased file, commits and
+   pushes that notes commit, then creates an annotated `v*` tag and GitHub
+   Release. The tag push triggers `.github/workflows/publish.yml`, which
+   builds the package, generates SLSA provenance attestations, and publishes
+   to PyPI via trusted publishing.
+
+Record release-worthy changes in `CHANGELOG/unreleased.md` as they merge.
+Projects generated before this changelog lifecycle was introduced remain
+compatible when they already have a versioned changelog file.
+
+## Code of Conduct
+
+Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.

extended_stats-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026, Djem Andreif Reyes
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

extended_stats-0.1.0/PKG-INFO

@@ -0,0 +1,103 @@
+Metadata-Version: 2.5
+Name: extended_stats
+Version: 0.1.0
+Summary: Python Boilerplate contains all the boilerplate you need to create a Python package.
+Project-URL: bugs, https://github.com/dreireyez/extended_stats/issues
+Project-URL: changelog, https://github.com/dreireyez/extended_stats/releases
+Project-URL: documentation, https://dreireyez.github.io/extended_stats/
+Project-URL: homepage, https://github.com/dreireyez/extended_stats
+Author-email: Djem Andreif Reyes <contact.dafreyes@gmail.com>
+Maintainer-email: Djem Andreif Reyes <contact.dafreyes@gmail.com>
+License: MIT
+License-File: LICENSE
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Typing :: Typed
+Requires-Python: >=3.9
+Requires-Dist: numpy>=1.24.0
+Requires-Dist: pandas>=2.0.0
+Requires-Dist: rich
+Requires-Dist: typer
+Description-Content-Type: text/markdown
+
+# Extended Statistics
+
+[![PyPI version](https://img.shields.io/pypi/v/extended_stats.svg)](https://pypi.org/project/extended_stats/)
+[![PyPI downloads](https://static.pepy.tech/badge/extended_stats/month)](https://pepy.tech/projects/extended_stats)
+
+**Extended Statistics** is a lightweight toolkit for comparing, profiling, and cleaning pandas DataFrames. It combines dataset diffing, an extended summary, and a handful of common cleaning transformations into a single, subpackage-organized API — built as a proof of concept for practicing Python package development fundamentals (structure, subpackages, testing, and packaging).
+
+* [GitHub](https://github.com/dreireyez/extended_stats/) | [PyPI](https://pypi.org/project/extended_stats/) | [Documentation](https://dreireyez.github.io/extended_stats/)
+* Created by **Djem Andreif Reyes**
+* MIT License
+
+## Features
+
+* **Dataset diffing:** Compare two versions of a DataFrame and get a structured report of what changed: rows added/removed, columns added/removed, dtype changes, per-cell value changes (when a key column is provided), and shifts in summary statistics (mean/median/nulls) for numeric columns.
+* **Human-readable diff summaries:** Turn a diff report into a plain-language sentence summary, no manual interpretation required.
+* **Dataset profiling:** A single function that merges the useful parts of .describe() and .info() into one report: shape, memory usage, duplicate row count, and per-column stats (nulls, uniques, mean/median/std for numeric columns, top value/frequency for categorical columns).
+* **Basic cleaning utilities:** Drop fully duplicate rows and standardize column names (lowercase, trimmed, underscore-separated) in one call each.
+* **Subpackage-organized API:** Diffing, profiling, and cleaning each live in their own subpackage, with a top-level re-export layer so functions are accessible.
+
+## Installation
+
+### Stable Release
+
+To install **Extended Statistics**, run this command in your terminal:
+
+```sh
+uv add extended_stats
+```
+
+Or if you prefer to use `pip`:
+
+```sh
+pip install extended_stats
+```
+
+## From Source
+
+The source files for Extended Statistics can be downloaded from the [Github repo](https://github.com/dreireyez/extended_stats).
+
+You can either clone the public repository:
+
+```sh
+git clone https://github.com/dreireyez/extended_stats
+```
+
+Or download the [tarball](https://github.com/dreireyez/extended_stats/tarball/main):
+
+```sh
+curl -OJL https://github.com/dreireyez/extended_stats/tarball/main
+```
+
+Once you have a copy of the source, you can install it with:
+
+```sh
+cd extended_stats
+uv sync
+```
+
+## Usage
+
+To use **Extended Statistics** in a project:
+
+```python
+import extended_stats
+```
+
+## Documentation
+
+Full documentation is available on
+[GitHub Pages](https://dreireyez.github.io/extended_stats/).
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, testing, and
+documentation instructions.
+
+## Author
+
+**Extended Statistics** was created in **2026** by **Djem Andreif Reyes**.
+
+GitHub [@dreireyez](https://github.com/dreireyez) | PyPI [@dreireyez](https://pypi.org/user/dreireyez/)

extended_stats-0.1.0/README.md

@@ -0,0 +1,81 @@
+# Extended Statistics
+
+[![PyPI version](https://img.shields.io/pypi/v/extended_stats.svg)](https://pypi.org/project/extended_stats/)
+[![PyPI downloads](https://static.pepy.tech/badge/extended_stats/month)](https://pepy.tech/projects/extended_stats)
+
+**Extended Statistics** is a lightweight toolkit for comparing, profiling, and cleaning pandas DataFrames. It combines dataset diffing, an extended summary, and a handful of common cleaning transformations into a single, subpackage-organized API — built as a proof of concept for practicing Python package development fundamentals (structure, subpackages, testing, and packaging).
+
+* [GitHub](https://github.com/dreireyez/extended_stats/) | [PyPI](https://pypi.org/project/extended_stats/) | [Documentation](https://dreireyez.github.io/extended_stats/)
+* Created by **Djem Andreif Reyes**
+* MIT License
+
+## Features
+
+* **Dataset diffing:** Compare two versions of a DataFrame and get a structured report of what changed: rows added/removed, columns added/removed, dtype changes, per-cell value changes (when a key column is provided), and shifts in summary statistics (mean/median/nulls) for numeric columns.
+* **Human-readable diff summaries:** Turn a diff report into a plain-language sentence summary, no manual interpretation required.
+* **Dataset profiling:** A single function that merges the useful parts of .describe() and .info() into one report: shape, memory usage, duplicate row count, and per-column stats (nulls, uniques, mean/median/std for numeric columns, top value/frequency for categorical columns).
+* **Basic cleaning utilities:** Drop fully duplicate rows and standardize column names (lowercase, trimmed, underscore-separated) in one call each.
+* **Subpackage-organized API:** Diffing, profiling, and cleaning each live in their own subpackage, with a top-level re-export layer so functions are accessible.
+
+## Installation
+
+### Stable Release
+
+To install **Extended Statistics**, run this command in your terminal:
+
+```sh
+uv add extended_stats
+```
+
+Or if you prefer to use `pip`:
+
+```sh
+pip install extended_stats
+```
+
+## From Source
+
+The source files for Extended Statistics can be downloaded from the [Github repo](https://github.com/dreireyez/extended_stats).
+
+You can either clone the public repository:
+
+```sh
+git clone https://github.com/dreireyez/extended_stats
+```
+
+Or download the [tarball](https://github.com/dreireyez/extended_stats/tarball/main):
+
+```sh
+curl -OJL https://github.com/dreireyez/extended_stats/tarball/main
+```
+
+Once you have a copy of the source, you can install it with:
+
+```sh
+cd extended_stats
+uv sync
+```
+
+## Usage
+
+To use **Extended Statistics** in a project:
+
+```python
+import extended_stats
+```
+
+## Documentation
+
+Full documentation is available on
+[GitHub Pages](https://dreireyez.github.io/extended_stats/).
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, testing, and
+documentation instructions.
+
+## Author
+
+**Extended Statistics** was created in **2026** by **Djem Andreif Reyes**.
+
+GitHub [@dreireyez](https://github.com/dreireyez) | PyPI [@dreireyez](https://pypi.org/user/dreireyez/)

extended_stats-0.1.0/SECURITY.md

@@ -0,0 +1,32 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+If you find a security vulnerability in Extended Statistics, please report it through [GitHub's private vulnerability reporting](https://github.com/dreireyez/extended_stats/security/advisories/new). This keeps the details private while we work on a fix.
+
+Please include:
+
+- What you found and how to reproduce it
+- Which version you're using
+- Any relevant logs or output (redact secrets)
+
+## Security Measures
+
+This project ships with security hardening out of the box:
+
+- **CodeQL** scans public repositories for injection, SSRF, path traversal, and other dataflow vulnerabilities using the `security-extended` query suite. Private repositories can opt in after enabling GitHub Code Security.
+- **Zizmor** audits GitHub Actions workflows for excessive permissions, unpinned actions, credential exposure, and cache poisoning risks
+- **Dependabot** opens PRs for uv dependencies and SHA-pinned GitHub Actions, with a 7-day cooldown to avoid adopting compromised releases immediately
+- **All actions pinned by SHA** with version comments, not floating tags
+- **Minimal workflow permissions** (`permissions: {}` at the top level, scoped per job)
+- **`persist-credentials: false`** on checkout steps to prevent token leakage
+
+## Response Times
+
+This is a volunteer-maintained open source project. Security reports are taken seriously, but there are no guaranteed response times.
+
+**Enterprise support** is available, with priority response SLAs. Contact contact.dafreyes@gmail.com for details.
+
+## Supported Versions
+
+Security fixes are applied to the latest release on the `main` branch. There is no backport policy for older versions.