safedeps
SolidGate dependency installs (npm/pip/cargo/go/gem/maven/nuget) with OSV-backed advisory checks, approved-spec ledger, and post-install reorg rollback. Run `safedeps check <eco> <pkg>@<range>` before any install command.
Install
Quality Score: 81/100
Skill Content
Details
- Author
- aldegad
- Repository
- aldegad/safedeps
- Created
- 4 months ago
- Last Updated
- 4 days ago
- Language
- Shell
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
safedep
SafeDep protects developers and AI coding agents against malicious open source components. External components are the blindspot: developers and agents can inspect the code they own, not the packages, IDE extensions, Agent Skills, MCP servers, and GitHub repositories they pull in, and every one of those can carry a supply chain attack (Shai-Hulud, Miasma, S1ngularity). The toolset: vet (scan dependencies for malware and known vulnerabilities), PMG (block malicious npm/pip/other packages at install time), gryph (audit what AI coding agents read, write, and execute), xBom (AI- and SaaS-aware bill of materials), plus SafeDep Cloud, Endpoint Hub, and an MCP server for hosted governance and fleet visibility. Use this skill whenever the user wants to secure their dependencies, block or detect malicious packages, scan a repository for vulnerabilities, deploy SafeDep for a team, install or configure vet / PMG / gryph / xBom, monitor developer machines for malicious package installs, investigate package activity or a
unslop-guard
Install and run pre-ship guardrails that stop new AI-generated slop from re-entering a codebase - a warn-only pre-commit hook that blocks only on secrets, and a GitHub Actions workflow that runs the unslop audit on pull requests and fails on critical findings. Use when the user asks to prevent regressions, add a pre-commit or CI security check, or gate deploys on an audit.
gatekeeper
This skill should be used before installing a skill, plugin, or MCP server from someone else — when the user says "is this skill safe", "check this before I install it", "audit this skill", "vet this plugin", "should I trust this", "scan this for malicious code", or pastes a GitHub link to a skill they are about to add. Reports what a skill actually touches next to what it claims to do, so the gap is visible before it runs with your permissions.