flowharness-inspection
Inspection context — the static, local, deterministic agent-rules surface scanner. Provides the domain layer for classifying agent-rules surfaces (CLAUDE.md, .cursorrules, AGENTS.md, agent-harness bundles, etc.), reading and parsing them, running architectural drift/contradiction/divergence/risk checks, and scoring findings into a quarantine verdict and drift index.
This is an internal library package of the FlowHarness toolchain, published to PyPI as a transitive dependency of flowharness (the scan CLI) and flowharness-ci-runner. Install those packages instead of depending on flowharness-inspection directly.
Note: this package currently installs a top-level module named
inspection. Preferuvx(isolated environments) overpip installinto a shared venv until the 0.2 module-namespace rename lands.
License: Apache-2.0
Homepage: https://github.com/flowharness-ai
1 maintainer
Metadata
1 maintainer
Release files for flowharness-inspection 0.3.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 | Actions |
|---|---|---|---|---|
| flowharness_inspection-0.3.0.tar.gz | 89.8 kB | With provenance | Details for flowharness_inspection-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flowharness_inspection-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for flowharness_inspection-0.3.0-py3-none-any.whl |
Total release size: 210.6 kB
Release files / flowharness_inspection-0.3.0.tar.gz
| Download URL | flowharness_inspection-0.3.0.tar.gz |
|---|---|
| Size | 89.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e23fe1f4e6b7f467f008c54434f9b7a766883a07ff91fd593ed340ff66f21829
|
|
BLAKE2b-256 checksum How to use checksums |
88202786a8ec9bec5b599c558b53dda3b4bed61e56240eb0515252c233a14fc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Oct 6, 2026.
Transparency logRelease files / flowharness_inspection-0.3.0-py3-none-any.whl
| Download URL | flowharness_inspection-0.3.0-py3-none-any.whl |
|---|---|
| Size | 120.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
df6d1128ab127a4cfd865d12f4c2822733a096f46360287f9112e775a0cce59e
|
|
BLAKE2b-256 checksum How to use checksums |
fbc98c3db9ed29372f35c9ddda3755b057f56208d07dd90e796b5e8dfaaf98b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Oct 6, 2026.
Transparency logSecurity for flowharness-inspection 0.3.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 flowharness_inspection-0.3.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 Oct 6, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
