deadpush 0.2.0__tar.gz

deadpush-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,36 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+env:
+  PYTHONUTF8: "1"
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          enable-cache: true
+
+      - name: Install dependencies
+        run: uv sync --extra dev
+
+      - name: Lint with ruff (non-blocking)
+        run: uv run ruff check deadpush/ tests/ || true
+
+      - name: Run tests
+        run: uv run pytest

deadpush-0.2.0/.github/workflows/python-publish.yml

@@ -0,0 +1,57 @@
+# This workflow will upload a Python Package to PyPI when a release is created.
+# Requires a PyPI trusted publisher configured for the project.
+# See: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries
+
+name: Upload Python Package
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  release-build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+
+      - name: Build release distributions
+        run: |
+          python -m pip install build
+          python -m build
+
+      - name: Upload distributions
+        uses: actions/upload-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+  pypi-publish:
+    runs-on: ubuntu-latest
+    needs:
+      - release-build
+    permissions:
+      id-token: write
+
+    environment:
+      name: pypi
+      url: https://pypi.org/project/deadpush/
+
+    steps:
+      - name: Retrieve release distributions
+        uses: actions/download-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+      - name: Publish release distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/

deadpush-0.2.0/.gitignore

@@ -0,0 +1,221 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+.deadpush/
+.deadpush-quarantine/
+.deadpush-archive/
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

deadpush-0.2.0/AGENT.md

@@ -0,0 +1,106 @@
+# deadpush — Agent Onboarding
+
+This project uses **deadpush**: an agent-native guardrail system that intercepts risky file writes in real time.
+
+## Quick Start
+
+- Write files normally via MCP (`write_file` tool). Guardrails run automatically.
+- If blocked → read the feedback file → fix the issue → retry.
+- If you hit a false positive → `add_allowed_pattern` to whitelist the code.
+
+## MCP Tools (24 available)
+
+Connect via `deadpush mcp` (stdio JSON-RPC on `2024-11-05` protocol).
+
+### Write / Check
+| Tool | What it does |
+|---|---|
+| `write_file(path, content)` | Write through guardrails. Blocked files go to quarantine + feedback. |
+| `check_file(path, content)` | Preview: would the file pass? Returns violations without writing. |
+
+### Scan
+| Tool | What it does |
+|---|---|
+| `scan` | Full analysis summary (dead symbols, debris, test issues, etc.) |
+| `get_dead_symbols` | Unreachable code |
+| `get_debris` | AI artifacts, stale files |
+| `get_test_issues` | No-assertion / tautology / empty tests |
+| `get_stale_docs` | Docstring-param mismatches |
+| `get_layer_violations` | Architectural import violations |
+| `get_security_boundaries` | Untested security-sensitive ops |
+| `get_complexity_alerts` | Complexity spikes |
+
+### Clean / Quarantine
+| Tool | What it does |
+|---|---|
+| `clean(mode)` | Remove dead code / debris (safe, dry_run, force) |
+| `quarantine_list(limit)` | List quarantined files |
+| `quarantine_restore(name)` | Restore from quarantine |
+
+### Feedback
+| Tool | What it does |
+|---|---|
+| `get_feedback(limit)` | Read recent guardrail feedback |
+| `get_status` | Current paths + available tools |
+| `get_safety_score` | Latest guardian score |
+
+### Config (agent self-service)
+| Tool | What it does |
+|---|---|
+| `get_runtime_config` | View all current rules |
+| `add_allowed_pattern(pattern, desc)` | Whitelist a regex pattern |
+| `remove_allowed_pattern(pattern)` | Remove from allowlist |
+| `ignore_path(path)` | Skip a file entirely |
+| `set_guardrail_level(category, level)` | Set severity: `off`, `warn`, or `block` |
+| `reset_runtime_config` | Clear all overrides to defaults |
+
+All tools return `{"success": bool, "data": ..., "summary": "..."}`.
+
+### Diff / Preview
+| Tool | What it does |
+|---|---|
+| `get_write_diff(path, content)` | Preview diff + guardrail violations before writing |
+| `allow_sensitive_write(path)` | Opt in to writing a sensitive config file (CI/CD, Docker, etc.) |
+
+## Guardrail Categories
+
+| Category | Default level | What it catches |
+|---|---|---|
+| `prompt_injection` | `block` | System prompt remnants, AI identity overrides, chat markup tokens |
+| `secret` | `block` | API keys, tokens, passwords, AWS keys, GitHub tokens |
+| `security` | `block` | eval/exec, subprocess, pickle, SQL injection, file deletion |
+| `layer` | `block` | Imports violating architecture layer rules |
+| `sensitive` | `block` | Writes to CI/CD, deployment, Docker, and other sensitive config files |
+| `destructive` | `warn` | Near-empty rewrites of substantial files, >50% line reduction |
+| `debris` | `warn` | TODO stubs, FIXME markers, bare `pass` statements |
+| `dependency` | `warn` | Typosquat packages, suspicious package names in dep files |
+
+## Self-Correction Flow
+
+```
+write_file("src/api.py", content)
+  ├─ ✅ Allowed → file appears at src/api.py
+  └─ ❌ Blocked → file quarantined, feedback written to .deadpush/feedback/
+
+Read feedback: get_feedback(5)
+Fix the issue in your code
+Retry: write_file("src/api.py", new_content)
+
+False positive? add_allowed_pattern("the_regex_that_matched")
+Then retry — it will pass.
+```
+
+## Runtime Config
+
+Persisted in `.deadpush/rules.json`. Survives server restarts.
+Modify via MCP tools above. Do NOT edit the file directly.
+
+Use `set_guardrail_level("prompt_injection", "warn")` to downgrade a category to warning-only (doesn't block, just reports).
+
+## What NOT To Do
+
+- Do NOT bypass guardrails by writing directly to the filesystem.
+- Do NOT edit `.deadpush/rules.json` directly — use the MCP tools.
+- Do NOT delete `.deadpush/` directory contents unless you understand the consequences.
+- Do NOT add `ignore all previous instructions` or similar prompt injection patterns to any file.
+- Do NOT commit secrets, API keys, or tokens to the repository.

deadpush-0.2.0/CHANGELOG.md

@@ -0,0 +1,16 @@
+# Changelog
+
+## 0.2.0 (2026-06-22)
+
+- Initial public release.
+- MCP server with 20+ tools for AI coding agents.
+- 7-category guardrail pipeline: security, secrets, prompt injection, debris, layer violations, destructive changes, sensitive writes.
+- Multi-factor dead code detection using 8 signals (call graph, registration, imports, reachability, git freshness, etc.).
+- Real-time filesystem guardian daemon (`deadpush protect --daemon`).
+- Staging-based write interception with quarantine + structured feedback.
+- Agent-as-adjudicator learning loop (adjudicate findings, learn false positives).
+- Path-aware severity lowering for test/mock files.
+- Runtime config system with per-category guardrail levels.
+- CLI: scan, clean, verify, quarantine, status, hooks, deps, init.
+- JSON-RPC 2.0 protocol compliance.
+- 300+ tests across 11 test files.

deadpush-0.2.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes
+- Focusing on what is best for the overall community
+
+Examples of unacceptable behavior:
+
+- The use of sexualized language or imagery, and sexual attention or advances
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information without explicit permission
+- Other conduct which could reasonably be considered inappropriate
+
+## Enforcement
+
+Project maintainers are responsible for clarifying and enforcing our standards.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the project team at harris@deadpush.dev. All complaints will be
+reviewed and investigated promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+[homepage]: https://www.contributor-covenant.org

deadpush-0.2.0/CONTRIBUTING.md

@@ -0,0 +1,38 @@
+# Contributing
+
+Thanks for your interest in deadpush.
+
+## Getting Started
+
+```bash
+git clone https://github.com/harris-ahmad/deadpush
+cd deadpush
+python -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev,watch,rich]"
+```
+
+## Running Tests
+
+```bash
+pytest
+```
+
+## Code Style
+
+We use ruff. Run before committing:
+
+```bash
+ruff check .
+```
+
+## Pull Requests
+
+- Keep changes focused. One PR = one concern.
+- Add tests for new functionality.
+- Run the full test suite before submitting.
+- Update CHANGELOG.md if the change is user-facing.
+
+## Questions?
+
+Open an issue at https://github.com/harris-ahmad/deadpush/issues

deadpush-0.2.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Harris Ahmad
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.