This release is a pre-release and may not be stable for production use.
pinky-core
Shared Python utilities for Snowflake development.
Part of the pinky-and-co suite.
Why pinky?
The modern data stack was built on a good idea — best of breed. One tool for ingestion, one for transformation, one for orchestration, one for observability.
The reality: more licenses, same delivery time, and most of your energy goes into the glue.
Snowflake collapsed the stack. Pinky makes it operational.
Do it right, and the credits follow.
Rationalized costs · Pure Python · Snowflake Native First
Install
pip install pinky-core
pip install "pinky-core[validate]" # with SIRET, IBAN, email, phone validators
pip install "pinky-core[address]" # with address parsing
Documentation
Explanation
API reference
Decisions
Structure
Show the directory tree
pinky-core/
├── .github/
│ └── workflows/
│ ├── ci.yml
│ ├── publish.yml
│ └── release.yml
├── .vscode/
│ └── settings.json
├── scripts/
│ ├── hooks/
│ │ ├── badges.toml
│ │ ├── check_forbidden_keywords.py
│ │ ├── check_snowpark_api.py
│ │ ├── check_typed_api.py
│ │ ├── check_weak_assertions.py
│ │ ├── check_zws.py
│ │ ├── commit-msg
│ │ ├── docs_identity.json
│ │ ├── generate-docs
│ │ ├── generate_ci_badges.py
│ │ ├── render_docs.py
│ │ └── run-tests
│ └── deploy_validate_udfs.py
├── sql/
│ └── deploy_udf_example.sql
├── src/
│ └── pinky_core/
│ ├── finance/
│ │ ├── __init__.py
│ │ └── fec.py
│ ├── __init__.py
│ ├── files.py
│ ├── fmt.py
│ ├── html.py
│ ├── lint.py
│ ├── schedule.py
│ ├── security.py
│ ├── sql.py
│ ├── validate.py
│ ├── warnings.py
│ └── xml.py
├── tests/
│ ├── fixtures/
│ │ ├── golden/
│ │ │ ├── dl_card_basic.html
│ │ │ ├── dl_card_expiry.html
│ │ │ ├── generate_html_basic.html
│ │ │ ├── task_table_error.html
│ │ │ ├── task_table_no_snowsight.html
│ │ │ └── task_table_snowsight.html
│ │ └── cats_domination.xml
│ ├── __init__.py
│ ├── test_fec.py
│ ├── test_files.py
│ ├── test_fmt.py
│ ├── test_html.py
│ ├── test_lint.py
│ ├── test_public_api.py
│ ├── test_schedule.py
│ ├── test_security.py
│ ├── test_sql.py
│ ├── test_validate.py
│ ├── test_warnings.py
│ └── test_xml_xpath.py
├── .gitignore
├── .gitleaks.toml
├── .pre-commit-config.yaml
├── .python-version
├── .secrets.baseline
├── CONTEXT.md
├── LICENSE
├── pyproject.toml
├── README.md
└── uv.lock
License
MIT — see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for pinky-core 0.1.0.dev9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pinky_core-0.1.0.dev9.tar.gz | 205.8 kB | With provenance | Details for pinky_core-0.1.0.dev9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pinky_core-0.1.0.dev9-py3-none-any.whl | Python 3 | none | any | Details for pinky_core-0.1.0.dev9-py3-none-any.whl |
Total release size: 255.6 kB
Release files / pinky_core-0.1.0.dev9.tar.gz
| Download URL | pinky_core-0.1.0.dev9.tar.gz |
|---|---|
| Size | 205.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38ec4f33d4fec8297be55f1eca05826a7b3275be24fe1148677fc3baf6b6b134
|
|
BLAKE2b-256 checksum How to use checksums |
33474ed34e6946b1912a5023bf609f3b7d57364639ce039f287f8a70b7f69882
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logRelease files / pinky_core-0.1.0.dev9-py3-none-any.whl
| Download URL | pinky_core-0.1.0.dev9-py3-none-any.whl |
|---|---|
| Size | 49.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bff165b4d495353b96dbee1252ada262b5f0d75c6b6996434c976dd298c6e1fa
|
|
BLAKE2b-256 checksum How to use checksums |
72994c96eb8b592da667721643437816385290411e4788093a07ab9fa71a7c8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logSecurity for pinky-core 0.1.0.dev9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pinky_core-0.1.0.dev9.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
