This release is a pre-release and may not be stable for production use.
collective.metadataaudit
collective.metaaaudit logs metadata changes to Plone content objects transparently (for all content types). This add-on in in particular useful when you have to answer the question “who was doing what and when”.
Install and use this add-on with care. In particular ensure that its usage is compliant with your local privacy and data-protection legislation.
Features
logs all metadata changes (create and edit operations) for all Plone content types (Dexterity content-types only)
Installation
Install collective.metadataaudit by adding it to your buildout:
[buildout]
...
eggs =
collective.metadataaudit
and then running bin/buildout
Usage
Use the Logging entry from the Plone toolbar
Contribute
Issue Tracker: https://github.com/collective/collective.metadataaudit/issues
Source Code: https://github.com/collective/collective.metadataaudit
License
The project is licensed under the GPLv2.
1.0a1 (2020-11-23)
Initial release. [zopyx]
1 maintainer
Metadata
1 maintainer
Release files for collective.metadataaudit 1.0a1
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 |
|---|---|---|---|---|
| collective.metadataaudit-1.0a1.zip | 45.6 kB | Without provenance | Details for collective.metadataaudit-1.0a1.zip |
Release files / collective.metadataaudit-1.0a1.zip
| Download URL | collective.metadataaudit-1.0a1.zip |
|---|---|
| Size | 45.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
825b0b66a8768ab5f50744f68004a0ecd833b237a308878a5240eefb22395121
|
|
BLAKE2b-256 checksum How to use checksums |
3cd93fd55835b187e67327f028dc3dda5528fe8d8143f06a06fc84f01b4ec11e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.8
|
Security for collective.metadataaudit 1.0a1
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.
