kryptorious-depguard
Cross-ecosystem dependency auditor for Python + Node. One command, offline, CI-ready — catches the dependency problems your linter can't see:
- Undeclared imports — code imports a package you never declared (
import requestswith norequestsinrequirements.txt). Breaks in a clean install. - Unused dependencies — declared in
requirements.txt/package.jsonbut never imported. Bloats installs and attack surface. - Unpinned specifiers —
numpy(any) or^1.2.3(floating). Non-reproducible builds. - Lockfile drift —
package.jsondisagrees withpackage-lock.json/yarn.lock.
Why this exists
node-depcheck is Node-only. pipreqs regenerates a requirements file but doesn't audit it. pyflakes F401 only catches unused local names. No lightweight, offline, single-tool audits both ecosystems and emits SARIF for GitHub code-scanning in one pass. depguard does.
Install
pip install kryptorious-depguard
Usage
Audit the current directory (both ecosystems):
depguard check .
Python only, fail CI on any high-severity finding:
depguard check . --python --no-node --fail-on high
Emit SARIF for GitHub code-scanning:
depguard check . --format sarif --output depguard.sarif
JSON for custom pipelines:
depguard check . --format json
GitHub Action (inline)
- name: Dependency audit
run: |
pip install kryptorious-depguard
depguard check . --format sarif --output depguard.sarif --fail-on high
- name: Upload SARIF
uses: github/codeql-action/upload-sarif@v3
with:
sarif_file: depguard.sarif
Exit codes
--fail-on {high,medium,low,never} controls the CI gate. Default high: exits 1 when any high-severity finding exists (undeclared imports).
Premium
Free tier includes everything above. Premium ($9 lifetime) adds cloud SARIF upload to code-scanning dashboards, scheduled baseline diffs, and HTML trend reports: https://kryptorious.gumroad.com/l/jbvet
License
MIT — Kryptorious Quantum Biosciences, Inc.
Metadata
Release files for kryptorious-depguard 1.1.1
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 |
|---|---|---|---|---|
| kryptorious_depguard-1.1.1.tar.gz | 14.2 kB | Without provenance | Details for kryptorious_depguard-1.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kryptorious_depguard-1.1.1-py3-none-any.whl | Python 3 | none | any | Details for kryptorious_depguard-1.1.1-py3-none-any.whl |
Total release size: 28.0 kB
Release files / kryptorious_depguard-1.1.1.tar.gz
| Download URL | kryptorious_depguard-1.1.1.tar.gz |
|---|---|
| Size | 14.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb90fc5652b5faf75b87459f5d5eeff55e29a03bcce23758012d86c53ab3f77b
|
|
BLAKE2b-256 checksum How to use checksums |
46a8a4a4ba533231155d30fa15085bb3600652456046e4ad1a05048474306105
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / kryptorious_depguard-1.1.1-py3-none-any.whl
| Download URL | kryptorious_depguard-1.1.1-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bab950e0962a4a5e9089a9085f5343142d381199a6bf2478eef385603f58c681
|
|
BLAKE2b-256 checksum How to use checksums |
2f4916a95b32fdee10abd31103f4f2b558d77f1f873da80203dd17ab7471f8b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for kryptorious-depguard 1.1.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.