apron-scim
Stateless server-side SCIM 2.0 protocol library — the service-provider role of RFC 7643/RFC 7644. It receives user and group provisioning from a customer identity provider and owns the protocol layer (schema, filter parsing, PATCH, request/response shaping), while the consumer supplies persistence and HTTP routing.
Part of the apron-* family of stateless protocol primitives.
Status: early scaffolding. The public API surface is being ratified (Epic 1) and features land per epic — see the issue backlog. Not yet published to PyPI.
Installation
uv add apron-scim
# or
pip install apron-scim
Scope
- In: SCIM service-provider protocol — resource/schema models, filter parsing (→ AST + visitor), PATCH application, discovery documents, and framework-agnostic request/response handlers.
- Out (by design): persistence, HTTP routing, and the outbound SCIM client. The
consumer implements a
ResourceStoreand wires its own routes.
Development
make setup # bootstrap uv, venv, and pre-commit hooks
make test # run the unit suite
make lint # run pre-commit (ruff, ruff-format, detect-secrets, ty, uv-lock)
License
Apache-2.0.
Metadata
Release files for apron-scim 0.0.1
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 | |
|---|---|---|---|---|
| apron_scim-0.0.1.tar.gz | 35.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apron_scim-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 45.2 kB
Release files / apron_scim-0.0.1.tar.gz
| Download URL | apron_scim-0.0.1.tar.gz |
|---|---|
| Size | 35.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb2e02254933e181304314f468e68c004c5d98b75dedf2ca81b26afa65f2df02
|
|
BLAKE2b-256 checksum How to use checksums |
ea51f1f04ceea79ce71a3e1ceee79cf64fb889e79e8a832f57502ee7f6543f42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 28, 2026.
Transparency logRelease files / apron_scim-0.0.1-py3-none-any.whl
| Download URL | apron_scim-0.0.1-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
730bee877631cc525abcf52e367f3edfeadaf76fce7268bb889ea47405022309
|
|
BLAKE2b-256 checksum How to use checksums |
2f61a796d896d5e78971fb8ee94e578785d27064848b18761801c86940beec6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 28, 2026.
Transparency logSecurity for apron-scim 0.0.1
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 2 files in this release have been uploaded with provenance metadata.
Attestation for apron_scim-0.0.1.tar.gz
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 Jul 28, 2026.
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.