PyTaskWireCheck 0.1.0__tar.gz → 0.1.1__tar.gz

{pytaskwirecheck-0.1.0/src/PyTaskWireCheck.egg-info → pytaskwirecheck-0.1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: PyTaskWireCheck
-Version: 0.1.0
+Version: 0.1.1
 Summary: Local-first, dependency-aware task orchestration engine (DAG scheduler + content-addressed cache + CLI).
 Author: Georgi Mullassery
 License-Expression: MIT
@@ -59,6 +59,29 @@ or a single byte leaving your machine.
 
 ---
 
+> **Not to be confused with the security tools in this family ([PyDeepMesh](https://github.com/Mullassery/PyDeepMesh), [PyDependencyCheck](https://github.com/Mullassery/PyDependencyCheck)):** despite the "Check" in its name, PyTaskWireCheck is a local task orchestrator, not a security scanner.
+
+## Which project do I need?
+
+Part of the Mullassery open-source family. These tools have similar names — here is the short version of who does what:
+
+| If you need to… | Use |
+| --- | --- |
+| Build a repository's dependency graph and match it against vulnerability advisories (Python, Rust, Node, containers) | [PyDeepMesh](https://github.com/Mullassery/PyDeepMesh) |
+| Understand *why* a Python dependency exists, who added it, and whether it is actually used | [PyDependencyCheck](https://github.com/Mullassery/PyDependencyCheck) |
+| Statically analyze a **dbt** project (risky tests, test blast radius, cost) | [PyDBTGuard](https://github.com/Mullassery/PyDBTGuard) |
+| Statically analyze **Apache Beam / Dataflow** pipelines (cost, hot keys, reliability) | [PyBeamGuard](https://github.com/Mullassery/PyBeamGuard) |
+| Validate **Airflow** DAGs and dbt runs | [PyAirflowTester](https://github.com/Mullassery/PyAirflowTester) |
+| Simulate cascading-failure **blast radius** across infrastructure, data pipelines, and AI systems | [PyBlastRadius](https://github.com/Mullassery/PyBlastRadius) |
+| Check the **quality of the data itself** at runtime (schema, drift, anomalies) | [StatGuardian](https://github.com/Mullassery/StatGuardian) |
+| Discover **devices, services, and vulnerabilities on a network** | [PyNetworkIntel](https://github.com/Mullassery/PyNetworkIntel) |
+| Discover and score **API security** risk (real traffic, agent/MCP, Cedar policy) | [PyAPICheck](https://github.com/Mullassery/PyAPICheck) |
+| Trace and root-cause **AI agent** failures | [PyAgentHound](https://github.com/Mullassery/PyAgentHound) |
+| Diagnose **RAG retrieval** failures | [PyVectorHound](https://github.com/Mullassery/PyVectorHound) |
+| Orchestrate **local, dependency-aware tasks** (DAG scheduler + content-addressed cache) | [PyTaskWireCheck](https://github.com/Mullassery/PyTaskWireCheck) |
+
+[Browse all projects →](https://github.com/Mullassery?tab=repositories)
+
 ## Why PyTaskWireCheck
 
 Most build tools want to own your project. PyTaskWireCheck does one job: it orchestrates

{pytaskwirecheck-0.1.0 → pytaskwirecheck-0.1.1}/README.md

@@ -19,6 +19,29 @@ or a single byte leaving your machine.
 
 ---
 
+> **Not to be confused with the security tools in this family ([PyDeepMesh](https://github.com/Mullassery/PyDeepMesh), [PyDependencyCheck](https://github.com/Mullassery/PyDependencyCheck)):** despite the "Check" in its name, PyTaskWireCheck is a local task orchestrator, not a security scanner.
+
+## Which project do I need?
+
+Part of the Mullassery open-source family. These tools have similar names — here is the short version of who does what:
+
+| If you need to… | Use |
+| --- | --- |
+| Build a repository's dependency graph and match it against vulnerability advisories (Python, Rust, Node, containers) | [PyDeepMesh](https://github.com/Mullassery/PyDeepMesh) |
+| Understand *why* a Python dependency exists, who added it, and whether it is actually used | [PyDependencyCheck](https://github.com/Mullassery/PyDependencyCheck) |
+| Statically analyze a **dbt** project (risky tests, test blast radius, cost) | [PyDBTGuard](https://github.com/Mullassery/PyDBTGuard) |
+| Statically analyze **Apache Beam / Dataflow** pipelines (cost, hot keys, reliability) | [PyBeamGuard](https://github.com/Mullassery/PyBeamGuard) |
+| Validate **Airflow** DAGs and dbt runs | [PyAirflowTester](https://github.com/Mullassery/PyAirflowTester) |
+| Simulate cascading-failure **blast radius** across infrastructure, data pipelines, and AI systems | [PyBlastRadius](https://github.com/Mullassery/PyBlastRadius) |
+| Check the **quality of the data itself** at runtime (schema, drift, anomalies) | [StatGuardian](https://github.com/Mullassery/StatGuardian) |
+| Discover **devices, services, and vulnerabilities on a network** | [PyNetworkIntel](https://github.com/Mullassery/PyNetworkIntel) |
+| Discover and score **API security** risk (real traffic, agent/MCP, Cedar policy) | [PyAPICheck](https://github.com/Mullassery/PyAPICheck) |
+| Trace and root-cause **AI agent** failures | [PyAgentHound](https://github.com/Mullassery/PyAgentHound) |
+| Diagnose **RAG retrieval** failures | [PyVectorHound](https://github.com/Mullassery/PyVectorHound) |
+| Orchestrate **local, dependency-aware tasks** (DAG scheduler + content-addressed cache) | [PyTaskWireCheck](https://github.com/Mullassery/PyTaskWireCheck) |
+
+[Browse all projects →](https://github.com/Mullassery?tab=repositories)
+
 ## Why PyTaskWireCheck
 
 Most build tools want to own your project. PyTaskWireCheck does one job: it orchestrates

{pytaskwirecheck-0.1.0 → pytaskwirecheck-0.1.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "PyTaskWireCheck"
-version = "0.1.0"
+version = "0.1.1"
 description = "Local-first, dependency-aware task orchestration engine (DAG scheduler + content-addressed cache + CLI)."
 readme = "README.md"
 license = "MIT"

{pytaskwirecheck-0.1.0 → pytaskwirecheck-0.1.1/src/PyTaskWireCheck.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: PyTaskWireCheck
-Version: 0.1.0
+Version: 0.1.1
 Summary: Local-first, dependency-aware task orchestration engine (DAG scheduler + content-addressed cache + CLI).
 Author: Georgi Mullassery
 License-Expression: MIT
@@ -59,6 +59,29 @@ or a single byte leaving your machine.
 
 ---
 
+> **Not to be confused with the security tools in this family ([PyDeepMesh](https://github.com/Mullassery/PyDeepMesh), [PyDependencyCheck](https://github.com/Mullassery/PyDependencyCheck)):** despite the "Check" in its name, PyTaskWireCheck is a local task orchestrator, not a security scanner.
+
+## Which project do I need?
+
+Part of the Mullassery open-source family. These tools have similar names — here is the short version of who does what:
+
+| If you need to… | Use |
+| --- | --- |
+| Build a repository's dependency graph and match it against vulnerability advisories (Python, Rust, Node, containers) | [PyDeepMesh](https://github.com/Mullassery/PyDeepMesh) |
+| Understand *why* a Python dependency exists, who added it, and whether it is actually used | [PyDependencyCheck](https://github.com/Mullassery/PyDependencyCheck) |
+| Statically analyze a **dbt** project (risky tests, test blast radius, cost) | [PyDBTGuard](https://github.com/Mullassery/PyDBTGuard) |
+| Statically analyze **Apache Beam / Dataflow** pipelines (cost, hot keys, reliability) | [PyBeamGuard](https://github.com/Mullassery/PyBeamGuard) |
+| Validate **Airflow** DAGs and dbt runs | [PyAirflowTester](https://github.com/Mullassery/PyAirflowTester) |
+| Simulate cascading-failure **blast radius** across infrastructure, data pipelines, and AI systems | [PyBlastRadius](https://github.com/Mullassery/PyBlastRadius) |
+| Check the **quality of the data itself** at runtime (schema, drift, anomalies) | [StatGuardian](https://github.com/Mullassery/StatGuardian) |
+| Discover **devices, services, and vulnerabilities on a network** | [PyNetworkIntel](https://github.com/Mullassery/PyNetworkIntel) |
+| Discover and score **API security** risk (real traffic, agent/MCP, Cedar policy) | [PyAPICheck](https://github.com/Mullassery/PyAPICheck) |
+| Trace and root-cause **AI agent** failures | [PyAgentHound](https://github.com/Mullassery/PyAgentHound) |
+| Diagnose **RAG retrieval** failures | [PyVectorHound](https://github.com/Mullassery/PyVectorHound) |
+| Orchestrate **local, dependency-aware tasks** (DAG scheduler + content-addressed cache) | [PyTaskWireCheck](https://github.com/Mullassery/PyTaskWireCheck) |
+
+[Browse all projects →](https://github.com/Mullassery?tab=repositories)
+
 ## Why PyTaskWireCheck
 
 Most build tools want to own your project. PyTaskWireCheck does one job: it orchestrates

{pytaskwirecheck-0.1.0 → pytaskwirecheck-0.1.1}/src/pytaskwirecheck/__init__.py

@@ -6,7 +6,7 @@ The public API is intentionally small: load a workflow, inspect its plan, and
 run it. See :mod:`pytaskwirecheck.api` for details.
 """
 
-__version__ = "0.1.0"
+__version__ = "0.1.1"
 
 from pytaskwirecheck.api import (  # noqa: E402
     Workflow,

{pytaskwirecheck-0.1.0 → pytaskwirecheck-0.1.1}/src/pytaskwirecheck/cache/store.py

@@ -286,7 +286,7 @@ class CacheStore:
         if not task.cache_eligible:
             return {
                 "eligible": False,
-                "reason": "task declares no inputs or outputs",
+                "reason": "task declares no outputs",
             }
         fp = self.fingerprint(task, dependency_keys)
         entry = self._entries / fp.key

{pytaskwirecheck-0.1.0 → pytaskwirecheck-0.1.1}/src/pytaskwirecheck/config/schema.py

@@ -98,12 +98,14 @@ class TaskConfig:
     def cache_eligible(self) -> bool:
         """Whether the task may produce/consume cache entries.
 
-        A task with no declared inputs and no declared outputs is treated as
-        non-cacheable by default, because PyTaskWireCheck cannot know what it touches.
+        A task must declare at least one output to be cacheable. An
+        input-only task has nothing to store, so marking it eligible would
+        advertise a cache entry that :meth:`CacheStore.store` never writes
+        (PyTaskWireCheck cannot know what result to restore).
         """
         if not self.cache:
             return False
-        return bool(self.inputs or self.outputs)
+        return bool(self.outputs)
 
 
 @dataclass(frozen=True)