Loss of provenance

A previous release had provenance metadata, but this release does not. View details.

dsw-tdk

Template Development Kit for Data Stewardship Wizard

Installation

Python package

You can easily install this tool using pip (from PyPI):

$ pip install dsw-tdk

Optionally, you can clone any version from this repository and install it directly:

$ git clone https://github.com/ds-wizard/dsw-tdk.git
$ pip install -e .

We recommend using virtual environments to avoid clashes in dependencies with other projects.

Dockerized tool

If you don't want to use Python directly on your machine, you can easily use Docker image with DSW TDK:

$ docker run datastewardshipwizard/dsw-tdk --help
$ docker run datastewardshipwizard/dsw-tdk:develop --help

See datastewardshipwizard/dsw-tdk on Docker Hub to check available tags.

Usage

You can find out possibilities directly using --help flag:

$ dsw-tdk --help
$ dsw-tdk put --help

For further information, visit our documentation.

Basic commands

new = create a new template project locally using interactive wizard
list = list templates available in configured DSW instance
get = download a template from DSW instance
put = upload a template to DSW instance (create or update)
verify = check the metadata of local template project
package = create a distribution ZIP package that is importable to DSW via web interface

Environment variables

You can use the following environment variables to avoid repeating CLI options.

DSW_API_URL = URL of DSW API you want to use, e.g., https://api.demo.ds-wizard.org (notice that it is not the URL of client, you can find it out by clicking Help > About in DSW)
- Used when --api-url not specified
DSW_API_KEY = API Key of the user authorized to manage document templates
- Used when --api-key not specified

You can also use them in .env file which is automatically loaded from current directory or specify it using --dot-env option:

$ ls -a
. .. .env my-other-file
$ dsw-tdk list
$ dsw-tdk --dot-env /path/to/my/.env list

How to start

Prepare your DSW instance and admin account (optionally, prepare .env file)
Verify the connection by issuing dsw-tdk list
Create a new template project dsw-tdk new or get existing dsw-tdk get (or re-use some local)
Go to the template project and make edits you need to do
Update template in DSW with dsw-tdk put (or continually with dsw-tdk put --watch)
(or) Create a distribution ZIP package that is importable via DSW web interface with dsw-tdk package

Verbosity

You can use --quiet and --debug flags to toggle less or more output messages:

$ dsw-tdk --quiet list
$ dsw-tdk --debug list

Requirements

Python 3.8+
DSW instance with matching version (e.g. a local one using Docker)
Admin credentials (email+password) to the DSW instance

Contributing

We welcome any form of feedback and contribution to this tool:

Report bugs or ask in case of uncertainty using GitHub Issues.
Share ideas and feature requests using DSW Ideas site.
Submit enhancements using Pull Requests, just please make sure that you comply with used conventions.

For more information read CONTRIBUTING.

License

This project is licensed under the Apache 2 License - see the LICENSE file for more details.

Metadata

Release files for dsw-tdk 4.33.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Loss of provenance

These files do not have provenance metadata, despite files in a prior release including this data.

We recommend further investigation before installing these files. View details.

Source distribution (sdist)

Source distribution for dsw-tdk 4.33.1
File	Size	Uploaded	Provenance
dsw_tdk-4.33.1.tar.gz	25.6 kB	Sep 13, 2026	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for dsw-tdk 4.33.1
File	Interpreter	ABI	Platform	Reset
dsw_tdk-4.33.1-py3-none-any.whl 31.0 kB Sep 13, 2026 Without provenance	Python 3	none	any	Details

Total release size: 56.6 kB

Release files / dsw_tdk-4.33.1.tar.gz

Loss of provenance

This file belongs to a release without provenance metadata, despite a prior release including this data.

We recommend further investigation before installing this file. View details.

Download URL	dsw_tdk-4.33.1.tar.gz
Size	25.6 kB
Tags	Source
SHA-256 checksum How to use checksums	`bca2b76ec39c34a8ac30c961f3cc7c9eaa4d41f711fef367f734ad1207d8be19`
BLAKE2b-256 checksum How to use checksums	`bcb1eea10adc061362b9a60bf55aa61303aa20688a37ea7c083940f1bae52180`
Upload date	Sep 13, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Release files / dsw_tdk-4.33.1-py3-none-any.whl

Loss of provenance

This file belongs to a release without provenance metadata, despite a prior release including this data.

We recommend further investigation before installing this file. View details.

Download URL	dsw_tdk-4.33.1-py3-none-any.whl
Size	31.0 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`9fa8714f595a5d844d0b6db91e158a7a0bc53f43ea20ceb9a4e04733e9d56599`
BLAKE2b-256 checksum How to use checksums	`44be74e204093041a06b9492253aae363141c2a0a7f2dec88244079fa9b3419b`
Upload date	Sep 13, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Security for dsw-tdk 4.33.1

Report project as malware

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.

Loss of provenance

A previous release of these files had provenance metadata, but this release does not.

While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.

Release comparison

Removed 4.34.0 2 files With provenance
Added 4.33.1 2 files Without provenance

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.