dependency-conflict-resolver-e0637f — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited dependency-conflict-resolver-e0637f (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Untangle "could not resolve dependency" hell into a clear, ranked plan.
Infer the package manager and ecosystem from the error or files mentioned; label assumptions (assumed — confirm). Always deliver a concrete resolution path even from just the error text.
The install error / conflict output, plus (if given) the manifest (package.json, requirements.txt, go.mod…) and lockfile, and the manager. Infer what's missing.
Plain-English: package A needs X of C, package B needs Y of C, and they can't both be satisfied (name the actual packages/versions from the input).
overrides, resolutions, constraints file) with the exact snippet — and the risk it carries.--legacy-peer-deps / --force — clearly flagged as masking the problem, not fixing it.Give the exact commands/edits for each, and a recommendation of which to pick and why.
How to confirm the fix (npm ls <pkg>, a clean reinstall, the build), and one habit to avoid recurrence (lockfile committed, renovate/dependabot, version pinning policy).
--force/--legacy-peer-deps-style escapes are flagged as masking, not fixing--force / --legacy-peer-deps — it hides the conflict and breaks later~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.