This release is a pre-release and may not be stable for production use.
Kedro-DataSentinel
kedro-datasentinel is a kedro-plugin for seamless integration of Data Sentinel capabilities inside kedro projects. It enforces Kedro principles to make data quality and validation as production-ready as possible. Its core functionalities are:
-
Data Validation:
kedro-datasentinelenhances data quality for machine learning and data engineering pipelines. With minimal configuration, you can validate your datasets during a kedro run, both online (during pipeline execution) and offline (post-execution). -
Audit Logging: Track and monitor your pipeline executions with detailed audit logs. This feature provides visibility into your data processing workflows, making it easier to debug issues and ensure compliance.
-
Notification System: Get alerted when data quality issues arise. Configure notifications to be sent through various channels when validation checks fail.
How do I install kedro-datasentinel?
You can install kedro-datasentinel with pip:
pip install kedro-datasentinel
For development installation:
pip install --upgrade git+https://github.com/SumzCol/kedro-datasentinel.git
We recommend using a package manager (like conda) to create a virtual environment and to read kedro installation guide.
Getting started
To use kedro-datasentinel in your Kedro project:
- Install the package as described above
- Create a
datasentinel.ymlconfiguration file in your project'sconfdirectory - Configure your datasets with validation rules in your catalog
- Run your Kedro pipeline as usual
Features
Data Validation
kedro-datasentinel provides a flexible framework for validating your data:
- Online Validation: Validate data during pipeline execution
- Offline Validation: Validate data after pipeline execution leveraging the command
datasentinel validate -d <dataset_name> - Custom Checks: Create your own validation checks
- Integration with Data Sentinel: Leverage all the capabilities of Data Sentinel
Audit Logging
Track the execution of your Kedro pipelines with detailed audit logs:
- Node Execution: Log when nodes start, complete, or fail
- Input/Output Tracking: Record which datasets were used as inputs and outputs
- Error Logging: Capture exceptions and error messages
- Multiple Storage Options: Store audit logs in databases, files, or custom stores
Notification System
Get alerted when data quality issues arise:
- Email Notifications: Send emails when validation checks fail
- Custom Notifiers: Create your own notification channels
- Event-Based Triggers: Configure which events trigger notifications
Release and roadmap
The release history centralizes package improvements across time.
Disclaimer
This package is still in active development. We use SemVer principles to version our releases.
Can I contribute?
We'd be happy to receive help to maintain and improve the package. Any PR will be considered (from typo in the docs to core features add-on). Please check the contributing guidelines.
Main contributors
The following people actively maintain, enhance and discuss design to make this package as good as possible:
Metadata
Release files for kedro-datasentinel 0.0.1b2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kedro_datasentinel-0.0.1b2-py3-none-any.whl | Python 3 | none | any | Details for kedro_datasentinel-0.0.1b2-py3-none-any.whl |
Release files / kedro_datasentinel-0.0.1b2-py3-none-any.whl
| Download URL | kedro_datasentinel-0.0.1b2-py3-none-any.whl |
|---|---|
| Size | 19.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f918e54697bb15385dc151c3d19f7fcde55536ef64ad263b4b7084206aad32ad
|
|
BLAKE2b-256 checksum How to use checksums |
579fc230b57f795263787eede00fe32a4257b20c6b04150fdb0c3034ec2579e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Sep 1, 2025.
Transparency logSecurity for kedro-datasentinel 0.0.1b2
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 1 file in this release has been uploaded with provenance metadata.
Attestation for kedro_datasentinel-0.0.1b2-py3-none-any.whl
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 Sep 1, 2025.
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.