pwned-deps
PulseGate's liveness check found it on 9 Oct 2026; it is registered on GitHub and PyPI and has been in the index since 16 Jun 2026. How this is checked
Drop your lockfile in, find out if you're pwned. Compromised-package scanner backed by OSV.dev.
Inferred · not functionally tested
Overview
5 featuresPurpose: Detecting compromised or malicious packages in project dependencies to improve supply chain security.
Inferred · not functionally tested
Audience: software developers and security teams
Inferred · not functionally tested
Functions: data_extraction
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: unknown
Recorded constraints: pricing: open_source · license: Apache-2.0 · platforms: CLI · deployment: browser, cli
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: github.com. These links do not verify the individual claims.
pwned-deps is an Application security & vulnerability scanning project. Inferred · not functionally tested: It focuses on detecting compromised or malicious packages in project dependencies to improve supply chain security. Inferred · not functionally tested: It is built as an open-source project for software developers and security teams. Basis unknown · not verified: pwned-deps is open source under the Apache-2.0 license. Basis unknown · not verified: pwned-deps is available on the web and the command line.
It is developed by mkbhardwas12, and it first shipped in 2026. The project is developed in the open on GitHub with 163 stars and 48 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include compromised package scanning, OSV.dev integration, and lockfile analysis. Inferred · not functionally tested: Catalogued interfaces include a public API.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Compromised package scanning
- OSV.dev integration
- Lockfile analysis
- Supply chain security
- CLI tool
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
Frequently asked questions about pwned-deps
- What is pwned-deps?
- Inferred · not functionally tested: Pwned-deps focuses on detecting compromised or malicious packages in project dependencies to improve supply chain security. It is catalogued under Application security & vulnerability scanning on PulseGate.
- Who should use pwned-deps?
- Inferred · not functionally tested: pwned-deps is an open-source project built for software developers and security teams.
- Does pwned-deps have a free plan?
- Basis unknown · not verified: Yes — pwned-deps is open source under the Apache-2.0 license and free to use.
- What platforms does pwned-deps run on?
- Basis unknown · not verified: pwned-deps runs on the web and the command line.
- Is pwned-deps still active?
- PulseGate's liveness check found it on 9 Oct 2026. Its GitHub repository shows 48 commits in the last 90 days.
- What are alternatives to pwned-deps?
- Similar projects tracked by PulseGate include dep-age, depsentinel, and pkgscan.dep-agedepsentinelpkgscan
- Who develops pwned-deps?
- pwned-deps is developed by mkbhardwas12.
- When did pwned-deps launch?
- pwned-deps first shipped in 2026.
Similar projects
Closest matches by what these projects do