Alchemist Auditing
Alchemist auditing provides a facility for auditing changes to an object to a relational database. It automatically captures and records events for object added, modified, deleted. in addition if the respective packages are present it also records worklow events ( ore.workflow ) and versioning ( alchemist.versioning ).
All events record time, action, active user, in addition modification events capture field change descriptions, to allow for listing attributes changed.
Auditing can be done on either a per table or
0.3.4 - December 23rd, 2008
packaging fixes ( template not included in package data )
0.3.2 - December 17th, 2008
update package metadata / classifiers
don’t require active user for auditing functionality
automation api for adapter registration and recorder generation ( provideRecorder )
0.3.0 - June 1st, 2008
First public release
Metadata
Release files for alchemist.audit 0.3.4
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 | |
|---|---|---|---|---|
| alchemist.audit-0.3.4.tar.gz | 6.2 kB | Without provenance | Details |
Release files / alchemist.audit-0.3.4.tar.gz
| Download URL | alchemist.audit-0.3.4.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa5451c78a87479b83ea2aa00d7b1dc20aff2f718dbe3d65b605e5a75bd2abeb
|
|
BLAKE2b-256 checksum How to use checksums |
13dbac8be0685ffdb8e6bf89dae0241e03cc34bb333048008df1e453833a2494
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for alchemist.audit 0.3.4
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.