Fabricated references
Checks whether pinned GitHub Action commits and exact package versions resolve to real upstream objects instead of trusting a plausible-looking string.
depfence statically inspects dependencies, workflows, model files, and agent configuration for threats conventional CVE scanners were not designed to see.
$ depfence scan .
discovering lockfiles, workflows, model files, and agent configuration
LOCAL source inspection stays on this machine
STATIC package code is not executed
VERIFY dependency versions and GitHub Action references
INSPECT prompt injection, MCP, agent skills, and CI trust boundaries
REPORT table · JSON · SARIF · CycloneDX · SPDX
Illustrative command flow. Findings depend on the repository being scanned.
depfence complements established vulnerability scanners by covering the control plane around AI-assisted software development.
Checks whether pinned GitHub Action commits and exact package versions resolve to real upstream objects instead of trusting a plausible-looking string.
Inspects source, metadata, commits, and configuration for instructions intended to manipulate AI-assisted review and development workflows.
Looks for tool shadowing, credential exposure, suspicious instruction fetches, mutable definitions, and unsafe agent configuration.
Audits GitHub Actions for expression injection, excessive permissions, untrusted artifacts, mutable actions, and privileged workflow paths.
Examines model files, build hooks, manifests, and project metadata for executable formats, unsafe deserialization, and install-time behavior.
Produces human and machine-readable results for local review, CI gates, GitHub code scanning, and software bill-of-materials workflows.
Dependency security tooling should not become another execution path. depfence analyzes source and metadata statically; package code is not run, and source code is not sent to an analysis service.
One scanner surface, several ways to consume the evidence.
Analysis surfaces
Outputs and integration
Engineering proof, not a pitch
depfence is not a replacement for every security scanner. Established tools have broader vulnerability databases and deeper container-image coverage. Its role is to cover AI, agent, dependency, and workflow attack classes that sit outside traditional CVE matching.
The project is currently installed from source rather than PyPI. The repository documents network behavior, offline operation, limitations, and the tests behind its claims.
depfence is public because security engineering is easier to trust when the source, limitations, and verification work are visible.