🔷 ssot-views
Derived reports and graph projections for SSOT registries.
ssot-views provides reusable derived projections for SSOT registries.
These outputs are non-canonical views built from registry data. The registry JSON remains the source of truth; this package focuses on reports and graph exports derived from that source.
What this package owns
- validation and certification report builders
- summary projections
- graph export builders for JSON and DOT output
When to use this package
Use ssot-views when you want:
- reusable Python functions for building SSOT reports
- graph export payloads or DOT output outside the CLI
- a small library dedicated to derived, read-oriented views
Use another package when you want:
- ssot-registry for core runtime APIs and mutation/validation workflows
- ssot-cli for command-line rendering and file output
- ssot-contracts for packaged schemas and templates
- ssot-tui for interactive terminal browsing
- ssot-codegen for contract metadata regeneration
Install
python -m pip install ssot-views
For local development from this repository:
python -m pip install -e pkgs/ssot-views
Public API
The top-level package currently exports:
build_validation_reportbuild_certification_reportbuild_summarybuild_graph_jsonbuild_graph_dot
Programmatic usage
Build a summary projection:
from ssot_views import build_summary
summary = build_summary(registry)
print(summary)
Build validation and certification reports:
from ssot_views import build_certification_report, build_validation_report
validation = build_validation_report(
registry,
".ssot/registry.json",
failures=[],
warnings=[],
)
certification = build_certification_report(
registry,
".ssot/registry.json",
release_report={"passed": True, "boundary": {"id": "bnd:demo", "profile_ids": [], "feature_ids": []}},
)
Build graph exports:
from ssot_views import build_graph_dot, build_graph_json
graph_payload = build_graph_json(registry)
dot_text = build_graph_dot(registry)
Canonical vs derived outputs
- Canonical:
.ssot/registry.json - Derived: reports, summaries, graph exports, and similar projections
This distinction matters for workflow design: views are meant to be regenerated from canonical data, not edited as the source of truth.
Package relationships
- Package type: derived-view library
- Depends on: ssot-contracts
- Consumed by: ssot-codegen, library users, and any tooling that needs reusable reports or graph exports
If you are building reporting, analysis, or export tooling around SSOT registries, this package is the appropriate reusable layer.
1 maintainer
Metadata
1 maintainer
Release files for ssot-views 0.2.26
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 | |
|---|---|---|---|---|
| ssot_views-0.2.26.tar.gz | 7.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ssot_views-0.2.26-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.5 kB
Release files / ssot_views-0.2.26.tar.gz
| Download URL | ssot_views-0.2.26.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e12832e2e2b44d1a9882e2c3c2cbac2d6e9b1de893468a962b59328232415c9
|
|
BLAKE2b-256 checksum How to use checksums |
060d90fba6f9c65b686ac45a22cecd3d19c1b62969fed9afcd9d530daafb1650
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / ssot_views-0.2.26-py3-none-any.whl
| Download URL | ssot_views-0.2.26-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
015c5eddee97ef72b4be7df441470b037e311e95751d267bc3be1fa3d7e6fc20
|
|
BLAKE2b-256 checksum How to use checksums |
c9488c98d13c62ec352ec65e5f029a37c0d20aacbb3f8a010ba512bfd4fc2130
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for ssot-views 0.2.26
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.
