restatedev / restatedev/sdk-python
Add automated dependency license checking (Python + Rust)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 81
- Forks
- 22
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 2
Description
Context
As part of an OSS license due diligence review, we found that this repository has no automated mechanism to verify that dependency licenses are acceptable. This is a hybrid Python + Rust (maturin/PyO3) project, so both ecosystems need coverage.
Recommended approach
Rust side: cargo-deny
Add a deny.toml alongside the existing Cargo.toml:
[licenses]
allow = [
"MIT",
"Apache-2.0",
"Apache-2.0 WITH LLVM-exception",
"BSD-2-Clause",
"BSD-3-Clause",
"ISC",
"BSL-1.0",
"CC0-1.0",
"Zlib",
"Unicode-3.0",
"Unicode-DFS-2016",
"OpenSSL",
"0BSD",
]
confidence-threshold = 0.8
Add to CI:
- uses: EmbarkStudios/cargo-deny-action@v2
with:
command: check licenses
Python side: liccheck or pip-licenses
Option A: liccheck — add a [tool.liccheck] section to pyproject.toml:
[tool.liccheck]
authorized_licenses = [
"MIT License",
"Apache Software License",
"BSD License",
"ISC License (ISCL)",
"Python Software Foundation License",
"Mozilla Public License 2.0 (MPL 2.0)",
]
Run as: liccheck -r <requirements-file>
Option B: pip-licenses — run as a CI step:
pip-licenses --allow-only="MIT;Apache-2.0;BSD-2-Clause;BSD-3-Clause;ISC;PSF-2.0;MPL-2.0"
Note on the published wheel
The published restate-sdk wheel currently has dependencies = [] (zero Python runtime deps) — all deps are in optional extras ([openai], [adk], etc.). The Rust native extension has its dependencies statically compiled in. License checking is still valuable as a preventive measure and to cover the optional extras that users install.
Why this matters
An automated license gate ensures no strong copyleft (GPL, AGPL, SSPL) dependencies accidentally enter the dependency tree through routine updates to either the Rust or Python side.
Current state (as of 2026-03-16)
All current dependencies (146 Python, 113 Rust) are permissively licensed — this is purely a preventive measure.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Cargo.toml and pyproject.toml, then inspect the existing CI workflow to find where dependency checks belong. Compare the proposed liccheck and pip-licenses approaches for Python, and add cargo-deny for Rust using the listed license policies. Done means CI checks both ecosystems, including optional Python extras, and rejects disallowed licenses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100