AnomalyArmor Python SDK
Python SDK and CLI for AnomalyArmor data observability platform.
Installation
pip install anomalyarmor-cli
Quick Start
from anomalyarmor import Client
client = Client(
api_key="your-api-key",
api_url="https://api.anomalyarmor.com"
)
# List assets
assets = client.assets.list()
CLI Usage
# Configure credentials
anomalyarmor auth login
# List assets
anomalyarmor assets list
# Check freshness
anomalyarmor freshness summary
Data Quality
Metrics
Track quantitative metrics like row counts, null percentages, and distinct counts.
# Get metrics summary
summary = client.metrics.summary("asset-uuid")
print(f"Active metrics: {summary.active_metrics}")
# Create a row count metric
metric = client.metrics.create(
"asset-uuid",
metric_type="row_count",
table_path="catalog.schema.orders",
)
# Trigger capture
client.metrics.capture("asset-uuid", metric.id)
CLI:
anomalyarmor metrics summary <asset-uuid>
anomalyarmor metrics list <asset-uuid>
anomalyarmor metrics capture <asset-uuid> <metric-uuid>
Validity Rules
Define and monitor data quality rules like NOT_NULL, UNIQUE, REGEX, and RANGE checks.
# Get validity summary
summary = client.validity.summary("asset-uuid")
print(f"Failing rules: {summary.failing_rules}")
# Create a NOT NULL rule
rule = client.validity.create(
"asset-uuid",
rule_type="NOT_NULL",
table_path="catalog.schema.orders",
column_name="order_id",
severity="critical",
)
# Run a check
result = client.validity.check("asset-uuid", rule.id)
print(f"Status: {result.status}, Invalid: {result.invalid_count}")
CLI:
anomalyarmor validity summary <asset-uuid>
anomalyarmor validity list <asset-uuid>
anomalyarmor validity check <asset-uuid> <rule-uuid>
Referential Integrity
Monitor foreign key relationships and detect orphan records.
# List referential checks
checks = client.referential.list("asset-uuid")
# Create a referential check
check = client.referential.create(
"asset-uuid",
child_table_path="catalog.schema.orders",
child_column_name="customer_id",
parent_table_path="catalog.schema.customers",
parent_column_name="id",
)
# Execute check
result = client.referential.execute("asset-uuid", check.id)
print(f"Orphan count: {result.orphan_count}")
CLI:
anomalyarmor referential list <asset-uuid>
anomalyarmor referential execute <asset-uuid> <check-uuid>
Documentation
See docs.anomalyarmor.com for full documentation.
Metadata
Release files for anomalyarmor-cli 0.6.0
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 | |
|---|---|---|---|---|
| anomalyarmor_cli-0.6.0.tar.gz | 106.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| anomalyarmor_cli-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 203.0 kB
Release files / anomalyarmor_cli-0.6.0.tar.gz
| Download URL | anomalyarmor_cli-0.6.0.tar.gz |
|---|---|
| Size | 106.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
552051bd18f23f87636f00d2658b0a4389b4a0daa56ff7f8b337a792c165bfb1
|
|
BLAKE2b-256 checksum How to use checksums |
5e8e8bae004726e4217e2ec61587572ca5dd95b4e86410c8baca5c0406fc1198
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 25, 2026.
Transparency logRelease files / anomalyarmor_cli-0.6.0-py3-none-any.whl
| Download URL | anomalyarmor_cli-0.6.0-py3-none-any.whl |
|---|---|
| Size | 96.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a7747c4470bfff55bbf2aec835268290d0d76def83e9e3375ac2e9f82e2219e3
|
|
BLAKE2b-256 checksum How to use checksums |
25958b833ecb4da639ac8b65516bfd7b3bbf3d169566f6c749312a5d7e926ee6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 25, 2026.
Transparency logSecurity for anomalyarmor-cli 0.6.0
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 anomalyarmor_cli-0.6.0.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 May 25, 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.